method and system.

专利摘要:
A network topology is provided that includes several data centers for building blockchain blocks. Data centers can process different block subgroups and then send updates to each other with information about new blocks. In addition, some data centers may protect sensitive block body information and may only share block headers instead.
公开号:BR112019004571A2
申请号:R112019004571
申请日:2017-08-10
公开日:2019-06-11
发明作者:Thekadath Ajith；Mukherjee Suman
申请人:Visa Int Service Ass；
IPC主号:

专利说明:

METHOD AND SYSTEM
CROSS REFERENCE TO RELATED APPLICATIONS [001] This application is an international patent application that claims the benefit of the filing dates Patent Application No. US 62 / 490,487, filed on April 26, 2017, which is incorporated into this document by reference in its fullness for all purposes.
[002] This application is also partly a continuation of patent application No. US 15 / 283,930, filed on October 3, 2016, which claims the benefit of Provisional Patent Application No. US 62 / 294,825, filed on February 12, 2016, the indices that are all incorporated into this document by reference in their entirety for all purposes.
FUNDAMENTALS [003] There are many networks and applications for transferring information and assets. For example, there are networks designed to transfer access credentials, event tickets, property rights, currency, game credits, mobile phone minutes, digital media, etc. In addition, there are often multiple networks to transfer the same type of asset. For example, if someone wants to transfer an event ticket to a friend, they can choose one of several ticket transfer networks and applications.
[004] It can be beneficial to unify and simplify many types of transfer networks. For example, if all of the asset transfer networks for transferring mobile phone minutes were combined into a single global network, it could simplify the transfer process. Participants can have only one application configured for a network. In addition, it could simplify record keeping, since a network could keep track of where assets have been moved.
[005] However, unifying transfer networks can present
Petition 870190022368, of 03/08/2019, p. 28/158
2/114 new problems. For example, coordinating all transfers can be a big task and can be too big a burden for a network administrator. In addition, the network administrator may be able to view the details of each transfer. This can limit privacy for network participants and can transfer a lot of power to the network administrator.
[006] The modalities of the invention address these and other problems individually and collectively.
SUMMARY [007] One embodiment of the invention is directed to a method. The method comprises the creation, by the first data center computer, of a first block for a first blockchain. The first block includes a first block header and first block body. The method also includes sending a message to a second data center computer indicating that the first block was created for the first blockchain. The message includes the first block header, but not the first block body. The second data center computer adds the first block header to a second blockchain and does not add the first block body to the second blockchain.
[008] Another embodiment of the invention is directed to a first data center computer configured to perform the method described above.
[009] Another modality of the invention is directed to a method that comprises the creation, by a first data center computer, of a first block for a first blockchain. The first block includes a first block header and first block body. The method also includes sending a first message to a second data center computer indicating that the first block was created for the first blockchain. The message includes the first block header, but not the
Petition 870190022368, of 03/08/2019, p. 29/158
3/114 first block body. The method also includes receiving, by a second data center computer, the first message indicating that the first block was created for the first blockchain. The second data center computer can also create a second block for a second blockchain. The second block includes a second block header that is the same as the first block header and the second block does not include the first block body.
[0010] Another embodiment of the invention is directed to a system that includes a first data center computer and a second data center computer configured to perform the method described above.
[0011] Additional details on the modalities of the invention can be found in the Detailed Description and in the Figures.
BRIEF DESCRIPTION OF THE FIGURES [0012] FIG. 1 shows a block diagram of a system according to an embodiment of the invention.
[0013] FIG. 2 shows a block diagram of a computer of the administrative node according to an embodiment of the invention.
[0014] FIG. 3 shows a block diagram of a computer of the emitting node according to an embodiment of the invention.
[0015] FIG. 4 shows an example of an asset transfer network, according to an embodiment of the invention.
[0016] FIG. 5 shows a flow chart illustrating a method for providing a digital asset in an asset transfer network, according to the modalities of the invention.
[0017] FIG. 6 shows an example of an asset transfer network with additional details.
[0018] FIG. 7 shows a diagram of an example network topology that can be used with embodiments of the invention.
[0019] FIG. 8 shows a flow chart illustrating a method for
Petition 870190022368, of 03/08/2019, p. 30/158
4/114 processing of digital assets in an asset transfer network with multiple data centers, according to the modalities of the invention.
[0020] FIG. 9 shows a diagram of an asset transfer network with different groups of data centers, according to the modalities of the invention.
[0021] FIG. 10 shows a flow diagram illustrating a method for distributing ledger updates to data centers of different groups, according to the modalities of the invention.
[0022] FIG. 11 shows a diagram of blockchain accounting books that partially match, according to one embodiment of the invention.
DETAILED DESCRIPTION [0023] The modalities of the present invention are directed to a system and method for processing data elements using several data centers. Using multiple data centers and load balancing techniques, you can distribute the processing load and improve transfer efficiency.
[0024] In addition, each data center can maintain a separate network record, which can be in the form of a blockchain ledger. Data centers can update each other in relation to the respective data elements that they have processed and / or blocks that have been created. As a result, even though the data element submission and record keeping processes are distributed, data centers can synchronize their records, effectively acting as a large, single network.
[0025] Separating the administration of a network between several data centers may allow the use of special, localized configurations, rules and data restrictions. For example, in some modalities, a given data center may not share information from significant data elements or
Petition 870190022368, of 03/08/2019, p. 31/158
5/114 block bodies with other data centers, but you can still share record identifiers (for example, block headers) or other undefined data element labels with other data centers (for example, as record updates). As a result, sensitive registration information can be contained and protected, improving privacy for participants using this data center.
[0026] The modalities of the invention can be applied to transfer the value in an asset transfer network. The asset transfer network can be a universal network with which participating entities can be registered directly. A universal network can allow a sending financial institution to communicate and provide value (for example, a digital asset) directly to any receiving financial institution associated with the network. A digital asset can be a promise of value and the value can be settled at a later time. A universal network can also allow the unique identification of each enrolled entity (for example, by distributing unique identifiers to each entity during enrollment).
[0027] In some modalities, the asset transfer network may be an allowed network that allows only validated entities to participate in the network. For example, a central network administrator can validate financial institutions and other entities during enrollment. During validation, the administrator can ensure that enrollment entities are legitimate organizations that are filtered for compliance with network rules. The administrator can also implement standardized messaging procedures and communicate these procedures to registered entities.
[0028] The digital assets associated with a transfer of value can, in some modalities, be digitally signed by a sending entity and / or an administrative entity. The signature of
Petition 870190022368, of 03/08/2019, p. 32/158
6/114 sender can indicate that the digital asset was legitimately sent by the indicated sender and the administrator's signature can indicate that the digital asset has been approved and / or registered by the administrator. In some modalities, a digital signature may indicate that the digital asset has been transferred and that the value cannot be taken over.
[0029] Some modalities include a central settlement entity. The central settlement entity may allow the amount to be settled efficiently from a sending account at a sending financial institution to a recipient account at a receiving financial institution. A central settlement entity can include a central financial institution with multiple locations and multiple accounts). The central settlement entity may have at least one location and one account in each country in which it operates. As a result, the first financial institution may have an account (for example, a settlement account) with the central settlement entity in a first country and the second financial entity may have an account with the central settlement entity in a second country. Thus, in some embodiments, an international transfer may take place by transferring the first financial institution to the central settlement entity and then from the central settlement entity to the second financial institution. This means that, in some modalities, each financial institution that participates in the asset transfer network can only have an external account with the central settlement entity (for example, instead of multiple corresponding banking relationships). In some embodiments, the central settlement entity may only have a position instead of having different branches in different countries. In this case, financial institutions in other countries may still maintain corresponding accounts with the central settlement entity (for example, nostro accounts). In addition, in some embodiments, each financial institution may have different accounts at the central settlement entity for different currencies (e.g. 1, 5, 10,
Petition 870190022368, of 03/08/2019, p. 33/158
7/114 or 100 accounts, each holding a different type of currency). As a result, the financial institution can settle transactions with other financial institutions using the best suitable currency or a currency that both financial institutions have.
[0030] As can be seen, the modalities provide an asset transfer network with improved speed, security, reliability, transparency and efficiency. For example, a universal and allowed network can be well organized and can enable efficient messages and transfers directly between a sender and a recipient, regardless of location. This organization can reduce extra communications, as well as remove the mystery of several unknown correspondent banking relationships, present in decentralized legacy systems.
[0031] Central registration, verification of compliance by participating entities, standardized communications and universal identifiers that uniquely identify entities can facilitate a sense of trust in the network and participating entities. A distributed ledger can instill confidence that each participating entity has the same information about contracts and transfers that were made. Likewise, digitally signed digital assets can be highly reliable, as signatures can be validated to confirm that a digital asset is being legitimately transferred.
[0032] The high level of network trust and digitally signed digital assets can allow receiving financial institutions to make a received digital asset value immediately available in the recipient's account, even if the amount has not yet been settled. This means that a transferred amount can be made available almost immediately.
[0033] In modalities of the invention, to initiate an asset transfer, a user (or an institution representing the user) can instruct an issuing node in the asset transfer network to generate and supply
Petition 870190022368, of 03/08/2019, p. 34/158
8/114 the digital asset. The issuing node can digitally generate and sign the digital asset. The issuing node can also obtain approval and a second digital signature from an administrative node (for example, a central administrator for the network). The sending node can then deliver the digital asset to a recipient node (for example, directly or through distribution across the network). The recipient node can then deliver the digital asset to the recipient (or an institution that represents the recipient).
[0034] In alternative modalities, the digital asset can be generated and / or signed by an interaction platform (instead of the issuing node). The interaction platform can then supply the digital asset prepared for the issuing node or administrative node for distribution within the asset transfer network.
[0035] In both cases, a single push message can be used to provide a digital asset. This single message can have enough information and be reliable enough to replace one or more traditional transfer messages (for example, an authorization request message, an authorization response message, release messages and / or multiple bank transfer messages corresponding intermediaries), thereby improving message efficiency.
[0036] The modalities allow any type of suitable value to be sent on a digital asset. For example, a digital asset can represent a promise of monetary value, so that the digital asset can be used to make a payment. In addition, a digital asset can be used to provide access rights, such as an access entry code for a restricted area, tickets to an event, login credentials to access secure information, etc. A digital asset can also be used to transfer ownership, such as deeds of ownership, vehicle title, holdings in patents, as well as to provide credit, such as
Petition 870190022368, of 03/08/2019, p. 35/158
9/114 game credit, energy credits, mobile phone minutes and / or for any other suitable purpose.
[0037] Thus, the modalities of the invention provide an asset transfer platform that allows the direct and predictable exchange of value (for example, value represented by account data, cryptographically signed digital assets and support instructions). The platform also provides verification of compliance of participants (for example, banks and their customers). In some modalities, screening information about users is obtained from banks or other service providers. In addition, the modalities use smart contracts that can automatically and forcibly appropriate digital assets according to certain criteria (for example, forcibly liquidate after the digital asset is distributed on the network for 24 hours). For example, a financial institution may, during registration, agree to have a smart contract established when a digital asset is requested or generated.
[0038] Before discussing specific modalities of the invention, some terms can be described in detail.
[0039] A data element can refer to digital information. For example, a data element can be information that exists in binary form. In some embodiments, a data element can include information about anything that can be described in a record. For example, a data element can include any suitable type of digital information, such as medical data, biometric data, property data, academic credentials, product data, etc. A data element can also be used to describe an update, change or request. For example, a data element can include digital information about a change in a person's medical condition, an update on the number of sick days an employee has used, a request to validate or approve a transfer
Petition 870190022368, of 03/08/2019, p. 36/158
10/114 value or a promise to transfer a value from one entity to one entity. An example of a data element is a digital asset.
[0040] A digital asset can refer to digital content associated with a value. In some cases, the digital asset may also indicate a transfer of value. For example, a digital asset may include data that indicates a transfer of a currency amount (for example, fiat currency or crypto currency). In other modalities, the digital asset may correspond to other non-monetary values, such as data of access privileges (for example, a number of authorized uses or a period of time to access information) and proprietary data (for example, rights data digital).
[0041] In some modalities, a digital asset can be considered a reliable guarantee that a value will be provided (for example, a reliable IOU). For example, providing a digital asset to a recipient can be considered a promise that is reliable enough to replace authorization request / response messages and / or release messages during a transaction.
[0042] A digital asset can also include information about one or more digital asset attributes. For example, a digital asset may include information useful for transferring the value of one entity or account to another. A digital asset can also include shipping information (for example, information that identifies a shipping entity). In some embodiments, a digital asset may include one or more of a digital asset identifier, a value (for example, a quantity, an original currency type, a destination currency type), throughput information, a fee exchange rate, an invoice number, an order number, a time stamp, a shipping entity identifier (for example, a corporate sender ID), a shipping entity account number, an entity name information, shipping entity contact information
Petition 870190022368, of 03/08/2019, p. 37/158
11/114 (for example, an address, phone number, e-mail address, etc.), sending institution information (for example, a financial institution name, corporate ID and BIN), an entity identifier recipient (for example, a recipient corporate ID), a recipient entity account number, a recipient entity name, recipient entity contact information (for example, an address, phone number, email address , etc.) and / or receiving institution information (for example, name of a financial institution, corporate ID and BIN). When a digital asset is received, the recipient may have sufficient information to proceed with a settlement transaction for the amount indicated.
[0043] In some modalities, a digital asset may also include digital signatures and / or encryption keys for validation and entity identification. For example, a digital asset can include the digital signature of the issuing node and the public key, as well as the public key for an administrative node.
[0044] An asset transfer network can be a network for supplying and / or receiving digital assets. An asset transfer network can provide infrastructure to deliver digital assets in push messages. An asset transfer network can include one or more types of nodes. In some modalities, digital assets transmitted over an asset transfer network can be recorded in a transaction accounting book. An example of an asset transfer network is a blockchain network, in which a transaction ledger can take the form of a blockchain.
[0045] The term node can refer to a connection point. In some embodiments, a node can be a physical electronic device that is capable of creating, receiving or transmitting data. In other embodiments, a node can be a software module in a computing device, the module
Petition 870190022368, of 03/08/2019, p. 38/158
Software 12/114 a connection point on a communications network. In some embodiments, a node can be a computing device within an asset transfer network. A node may be able to create an asset, transfer an asset, receive an asset, validate an asset, maintain a transaction ledger and / or perform any other appropriate functions. Different types of nodes may be able to perform different sets of functions within an asset transfer network. In some embodiments, a node may be associated with and / or operated by a computer at the financial institution (for example, a bank), a payment processor computer, a third party computer, or any other appropriate entity.
[0046] A record can refer to the evidence of a data element. A digital record can be the electronic documentation of a data element. A record can include a record identifier and registration information. For example, registration information can include information from a data element (for example, a digital asset) and / or information about the data element (for example, a digital signature associated with the digital asset). A record identifier can be a number, title or other value used to identify a record. A record identifier can be undefined, where it may not provide any meaningful information about the record information in the record. Examples of records include medical records, academic records, transaction records within a transaction accounting book, etc. Another example of a record is a block on a blockchain. An individual block can be an individual record and a blockchain can be a series of records. A blockchain header is an example of a registration identifier and a blockchain body is an example of registration information.
[0047] The term transaction accounting book can refer to
Petition 870190022368, of 03/08/2019, p. 39/158
13/114 to a compilation of data from previous transactions. The transaction ledger can be a database or other comparable file structure that can be configured to store data for all digital asset transfers, including the date and time of the transfer, the amount of the transfer and identification information for participants in the transfer (for example, the sender and recipient of the transfer amount). In some embodiments, the transaction ledger may be in the form of an electronic ledger (for example, blockchain), in which the data already stored in the electronic ledger is unalterable. In some embodiments, each node within an asset transfer network can store its own copy of the transaction ledger. In other ways, only some of the nodes store their own copy of the transaction book. In other modalities, some of the nodes may have a restricted view of the transaction book. For example, some of the nodes may only be able to view and / or verify the transactions to which they were a part.
[0048] A transaction ledger may include digitally signed transaction records (for example, with a private key) to protect the transaction entries in the ledger from being tampered with false transaction data. This can prevent double spending and make all transactions immutable and irreversible and therefore make the ledger reliable.
[0049] In some modalities, a transaction accounting book may be publicly visible. For example, one or more entities may have access to the ledger and may be able to consult the ledger to determine whether a particular transaction actually occurred or whether a particular amount is authentic. In some modalities, the accounting book can only be partially
Petition 870190022368, of 03/08/2019, p. 40/158
14/114 viewable for one or more entities.
[0050] As used here, a blockchain can compose a series of blocks. Each block on the blockchain can include an electronic record of one or more historical transactions, as well as metadata. In some embodiments, blocks on the blockchain can be linked by including a reference to the preceding block (for example, a hash output from a preceding block). Each new block on the blockchain can be determined algorithmically based on new transactions and previous blocks on the blockchain. As a result, any tampering with the data stored in those earlier blocks can be detected.
[0051] A block can include a block body and a block header. The block header can be a block identifier or label. The block header can be used to identify the block and block headers can be used to link blocks. The block body can include the information stored in the block. For example, the registration information stored in a block can be considered the body of the block. The block body can also include other data, such as a reference to a previous block (for example, a previous block header), a timestamp, a random number, a hash of record information (for example, transaction) and / or any other appropriate information. In some embodiments, the block body can be all block data in addition to the block header. A block header can be created based on the block body. For example, some or all of the block body information can be used as input into a hash algorithm, encrypted or otherwise manipulated to create a block header. A previous block can be linked to a current block using the previous block header as in the input when generating the current block header.
[0052] A corporate ID can include an identifier for a
Petition 870190022368, of 03/08/2019, p. 41/158
15/114 person, company, institution or any other suitable entity. In some embodiments, a corporate ID can be a globally unique identifier. For example, corporate IDs can be issued by a central and trusted entity. A company can include alphanumeric characters, special characters and any other suitable symbol. In some embodiments, a corporate ID can be a unique use identifier, updated after each transaction. In some embodiments, a corporate ID can be used as an address to receive a digital asset transfer (for example, a corporate ID can be associated with an account).
[0053] A key pair may include a linked encryption key pair. For example, a key pair can include a public key and a corresponding private key. In a key pair, a first key (for example, a public key) can be used to encrypt a message, while a second key (for example, a private key) can be used to decrypt the encrypted message. In addition, a public key may be able to authenticate a digital signature created with the corresponding private key. The public key can be distributed across an entire network to allow authentication of signed messages using the corresponding private key. Public and private keys can be in any suitable format, including those based on RS A or elliptical curve encryption (ECC). In some embodiments, a key pair can be generated using an asymmetric key pair algorithm. However, a pair of keys can also be generated using other means, such as one commonly known in the art.
[0054] The term digital signature can refer to an electronic signature for a message. The digital signature can be a numeric value, an alphanumeric value or any other type of data including
Petition 870190022368, of 03/08/2019, p. 42/158
16/114 a graphic representation. A digital signature can be a unique value generated from a message and a private key using an encryption algorithm. In some embodiments, a validation algorithm using a public key can be used to validate the signature.
[0055] The term proof of zero knowledge or zero knowledge protocol can refer to a method of verifying information that is true without transmitting the information itself. In a zero knowledge protocol, secret information can be verified without being revealed. More information about zero knowledge tests can be found at:
J. Camenisch and M. Stadler. Proof systems for general statements about discrete logarithms. Technical Report TR 260, Institute for Theoretical Computer Science, ETH Zurich, March 1997.
[0056] In some embodiments, the verification of an obscured or partially obscured transaction ledger may employ a zero knowledge protocol.
[0057] A server computer can include a powerful computer or cluster of computers. For example, the server computer can be a large mainframe, a cluster of minicomputers, or a group of servers that function as a unit. In one example, the server computer can be a database server coupled to a web server. The server computer can be coupled to a database and can include any hardware, software, other logic or combination of the above to meet the requests from one or more client computers.
[0058] FIG. 1 shows a system 100 comprising a number of components. The system comprises a user computer 110 operated by a user (not shown). User computer 110 may be in communication with a computer of the sending institution 160, which
Petition 870190022368, of 03/08/2019, p. 43/158
17/114 can be associated with a sender node computer 165. System 100 also comprises a resource provider computer 130 associated with a resource provider (not shown). The computer of the resource provider 130 may be in communication with a computer of the receiving institution 140, which may be associated with a computer of the recipient node 145. The system further comprises an interaction platform 154, one or more computers of the administrative node 150, a foreign exchange transaction application interface 152, a settlement service computer 155, a transaction repository 156 and a risk management computer 157. Each of the entities in FIG. 1 can all be in operational communication with each other through any suitable communication channel or communications network. Communications networks can be any and / or a combination of the following: a direct interconnection; the Internet; a Local Area Network (LAN); a Metropolitan Area Network (MAN); an Operational Missions like Us on the Internet (OMNI); a secure personalized connection; a Wide Area Network (WAN); a wireless network (for example, employing protocols such as, but not limited to, a Wireless Application Protocol (WAP), I-mode and / or the like); and / or the like.
[0059] Messages between computers, networks and devices can be transmitted using secure communications protocols, such as, but not limited to, File Transfer Protocol (FTP); HyperText Transfer Protocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS), Secure Socket Layer (SSL), ISO (for example, ISO 8583) and / or similar.
[0060] System 100 can be used to process, approve and record any suitable type of data element. Individuals, organizations and any other suitable entity can submit requests to process and approve data elements and records can be created
Petition 870190022368, of 03/08/2019, p. 44/158
18/114 and updated for data elements.
[0061] For the sake of explanation, system 100 is mainly described below as a system that allows individuals, companies and other entities to transfer value to one another. System 100 can use push transaction messages that are digitally signed and verified by a trusted central entity. Transactions can also be recorded in a reliable accounting book (for example, a blockchain). As a result, push messages can be trusted and trusted. Push messages can serve as a replacement for typical authorization request messages, authorization response messages and / or compensation messages.
[0062] System 100 may include a network of nodes, such as the computer of administrative node 150, the computer of sender node 165 and the computer of recipient node 145. These nodes can, in combination, include an asset transfer network ( for example, a blockchain network). This asset transfer network can be used to provide any suitable type of digital asset, such as a digital payment asset (for example, for transferring monetary value) or a digital access asset (for example, for transferring access privileges. ).
[0063] As an example, system 100 can serve as a transaction system for providing payments. For the sake of explanation, the entire system 100 can be referred to as a transaction system and a central network of nodes (for example, one or more recipient node computers 145, one or more administrative node computers 150, and one or more computers sender node 165) can be referred to as an asset transfer network.
[0064] In this transaction system, the user can provide a payment to the resource provider. To do this, user computer 110 can instruct the sending institution computer 160 to
Petition 870190022368, of 03/08/2019, p. 45/158
19/114 transferring the value of a user account to the sending institution's computer 160. The sending institution's computer 160 can interact with the asset transfer network and request that a digital asset be sent to the resource provider. A digital asset can be a highly reliable promise of a transfer of value. Thus, when the receiving institution receives an official digital asset associated with the asset transfer network, the receiving institution can be informed and guaranteed that the amount will be transferred from the user's account to the resource provider's account. The amount can be settled between accounts at a later time (for example, through the settlement account at a central settlement bank).
[0065] For the sake of description, system 100 shows the examples of the user (associated with the user's computer 110) and the resource provider (associated with the resource provider's computer 130). The modalities also allow the amount to be sent to and from any suitable entity. For example, system 100 can host company-to-company payments, person-to-person payments and any other suitable type of transfer.
[0066] In order to participate in system 100, the user can register. For example, the user can (through the user's computer 110 and / or an interface provided by the sending institution's computer 160) subscribe to the asset transfer network. The asset transfer network that subscribes to the services can be provided by the interaction platform 154 and / or the computer of the administrative node 150. An asset transfer network administrator (for example, interaction platform 154) can associate a corporate ID with the user, user computer 110 or user account. In some embodiments, the sending institution's computer 160 can obtain a corporate ID of interaction platform 154 on behalf of the user.
[0067] The sending institution's computer 160 can store
Petition 870190022368, of 03/08/2019, p. 46/158
11/20 value on behalf of the user. The sending institution's computer 160 may also be able to provide value (for example, providing a payment) on behalf of the user. An example of a sending institution can be an issuer, which can normally refer to a business entity (for example, a bank) that issues and maintains an account (for example, a bank account) for a user.
[0068] A user account on the computer of the sending institution 160 can be associated with various user information. For example, a user's transaction account may be associated with a first name, a surname, a government-issued identification number, such as a driver's license number, passport number or social security number, date of birth, home address and / or business name, a phone number, an account username, an account password, an email address, etc.
[0069] The sending institution's computer 160 can also enroll with the asset transfer network (for example, through the computer of the administrative node 150 or the interaction platform 154) in order to interact with the network. As a result, the sending institution's computer 160 can also receive a unique corporate ID.
[0070] In some embodiments, the sending institution's computer 160 can also receive a key pair. This key pair can be stored in a hardware security module (HSM). In some embodiments, the sending institution's computer 160 can maintain its own HSM. Alternatively, the key pair of the sending institution's computer 160 may be stored in the HSM of another entity (for example, an HSM on the computer of the issuing node 165 or the computer of the administrative node 150).
[0071] The computer of the sending institution 160 may be associated and / or represented by the computer of the sending node 165, which may be able to
Petition 870190022368, of 03/08/2019, p. 47/158
21/114 provide payments (for example, through digital assets) on the asset transfer network on behalf of the sending institution's computer 160. [0072] As explained in more detail below, the modalities provide several ways for the institution's computer sending 160 to interact with the asset transfer network to request a transfer of value. For example, in some embodiments, the sending institution's computer 160 can work closely with the interaction platform 154, which can generate digital assets and interact with the asset transfer network on behalf of the sending institution's computer 160. In this scenario, the sending institution's computer 160 can instruct interaction platform 154 to initiate a transfer of the value from the user account to the resource provider account. The interaction platform 154 can then generate the digital asset, digitally sign the digital asset (for example, with one or more digital signatures based on one or more private keys) and then deliver the digital asset to the network transferring assets (for example, the computer for administrative node 150 or the computer for issuing node 165). The digital asset can then be distributed within the asset transfer network and registered.
[0073] In an alternative example, the sending institution computer 160 may instead work more closely with a computer from the sending node 165 that represents the computer from the sending institution 160. The computer from the sending node 165, instead of interaction platform 154, it can generate and sign digital assets on behalf of the sending institution's computer 160. However, in some modalities, interaction platform 154 can still play a role, providing an interface to the sending institution's computer 160 to communicate with the sender node computer 165. In this scenario, the sender institution computer 160 can instruct the sender node computer 165 to initiate a transfer of value from the user account to the sender account.
Petition 870190022368, of 03/08/2019, p. 48/158
22/114 resource provider. The computer of the issuing node 165 can then generate a digital asset indicating a transfer of funds from the user to the resource provider. The computer of the issuing node 165 can digitally sign the digital asset, obtain a second digital signature from the computer of the administrative node 150, and supply the digital asset to the computer of the recipient node 145. The computer of the recipient node 145 can supply the digital asset to the computer of the receiving institution 140.
[0074] In other modalities, the computer of the sending institution 160 can directly manage and control the computer of the issuing node 165 or can have whitewashed access to the asset transfer network (for example, the computer of the sending node 165 can be provided by another entity, but can be used by the sending institution's computer 160 for transactions). In any case, there may be a way for the sending institution's computer 160 to access the network and initiate transactions.
[0075] The interaction platform 154 may include one or more server computers. As mentioned above, interaction platform 154 can facilitate interaction between the asset transfer network and financial institutions (for example, the sending institution's computer 160 and the receiving institution's computer 140). For example, interaction platform 154 may include a platform and interface (for example, an application interface) that allows financial institutions and users to access the asset transfer network (for example, communicate with nodes on the network) [0076] The modalities allow the interaction platform 154 to assume a more active role performing tasks such as enrolling users, generating digital assets, signing digital assets, maintaining transaction records, etc. Other modalities allow the interaction platform 154 to assume a more passive role by performing fewer tasks and, instead, acting mainly as a communication interface between the network of
Petition 870190022368, of 03/08/2019, p. 49/158
11/23 asset transfer and financial institutions.
[0077] The interaction platform 154 can allow users (through user's computer 110) and financial institutions to sign up to participate with the asset transfer network and create a profile. The interaction platform 154 can also provide an interface where users and financial institutions can initiate a transaction, as well as display exchange rates and transfer fees, and receive reconciliation information for a transaction.
[0078] The interaction platform 154 can also keep a record of transactions that have occurred (for example, a list of transactions or a blockchain-type ledger). In addition, the interaction platform 154 can perform analysis of user and bank behavior. Users and financial institutions can be allowed to view analytics, view a global directory and view network compliance information.
[0079] As described above, the interaction platform 154 can also perform a series of services related to the generation of assets, digitally signed assets, storage of transaction records and any other suitable service. However, these services, instead, will be described below with respect to the computer of administrative node 165. This is because, in some embodiments, some or all of the functionality described below with respect to the computer of administrative node 150 may instead be performed by the interaction platform 154. Likewise, some or all of the functionality in relation to the interaction platform 154 can instead be performed by the computer of the administrative node 150. In addition, the interaction platform 154 and the computer of the administrative node 150 can be combined as a single entity. In some embodiments, the computer of administrative node 150 may be a node that is associated with interaction platform 154 and that participates in the asset transfer network on behalf of interaction platform 154 (for example,
Petition 870190022368, of 03/08/2019, p. 50/158
24/114 example, similar to the way the computer of the sending node 165 is associated with the computer of the sending institution 160).
[0080] The modalities allow the interaction platform 154 and the administrative node computer 150 to exchange functionality and / or be combined because, in some modalities, both entities can be associated and / or operated by the same management entity. This management entity (not shown in system 100) can be a central entity that administers system 100. Thus, interaction platform 154 and administrative node computer 150 can work together as different components of a network organizing entity. This management entity can be associated and / or operate several other entities in the system 100, such as the interaction platform 154, the foreign exchange transaction application interface 152, the settlement service computer 155, the transaction repository 156 and / or the risk management computer 157.
[0081] In some modalities, the management entity may also operate the asset transfer network. For example, the management entity may provide the issuing node computer 165, the administrative node computer 150e / or the recipient node computer 145. However, in other embodiments, a third party entity may provide the asset transfer network (for example, the management entity may outsource control of the asset transfer network). Even in this scenario, the management entity can still operate one or more nodes (for example, the computer for administrative node 150) or the management entity can communicate with a computer for administrative node 150 that represents the management entity within the network. transfer of fixed assets.
[0082] In some embodiments, the management entity may be a transaction processing entity (for example, one or more
Petition 870190022368, of 03/08/2019, p. 51/158
25/114 transaction processing computers). As an example, a transaction processing computer can include data processing subsystems, networks, and operations used to support and provide authorization services, exception file services, and clearing and settlement services. For example, the transaction processing computer may include a server coupled to a network interface (for example, via an external communication interface) and information databases. A transaction processing computer can represent a transaction processing network. An exemplary transaction processing network can include VisaNet ™. Transaction processing networks, such as VisaNet ™, are capable of processing credit card transactions, debit card transactions and other types of business transactions. VisaNet ™, in particular, includes a VIP (Visa Integrated Payments system) that processes authorization requests and a Base II system that performs clearing and settlement services. A transaction processing computer can use any suitable wired or wireless network, including the Internet.
[0083] The computer of administrative node 150 can manage the asset transfer network. As long as a computer from administrative node 150 is shown on system 100, there can be any suitable number of administrative nodes. In addition to acting as a node in the asset transfer network, the computer of administrative node 150 can also organize and ensure the reliability of the asset transfer network. The computer of administrative node 150 can be a trusted central entity. As a result, the asset transfer network administered by the computer of administrative node 150 can also be trusted. For example, as explained in more detail below, the asset transfer network can be a federated network.
Petition 870190022368, of 03/08/2019, p. 52/158
26/114 [0084] The computer of administrative node 150 can provide a series of services to facilitate the asset transfer network and the transaction system. For example, the computer of administrative node 150 can enroll nodes, service providers, users, etc. The computer of administrative node 150 can also provide corporate identifiers and key pairs for these enrolled entities. The administrative node computer 150 can also generate digital assets, validate new digital assets, provide digital signatures for new digital assets and maintain a transaction accounting book.
[0085] An example of an administrative node computer 150, according to some embodiments of the invention, is shown in FIG. 2. The administrative node computer 150 comprises a processor 150A, a network interface 150B, a node database 150C, a ledger database 150D, a key database 150P, a database of 150Q user and a 150E computer readable medium.
[0086] The 150E computer-readable medium may include a 150F enrollment module, a 150G verification module, a 150H risk module, a 150J validation module, a 150K signature module, a 150L ledger update module , a 150M digital asset module and any other suitable software module. The computer-readable medium 150E may also include code, executable by the processor 150A for the implementation of a method which comprises receiving, from a computer at the sending node, a request to validate a digital asset, including a first digital signature, in that the first digital signature was generated with a first private key associated with the computer of the issuing node and where the digital asset indicates the transfer of a value from a sender to a recipient; validate the digital asset; generate a second digital signature for the digital asset, the second digital signature generated with a second associated private key
Petition 870190022368, of 03/08/2019, p. 53/158
11/27 to the administrative node computer; provide the second digital signature to the computer of the sending node, where the computer of the sending node sends the digital asset to a computer of the receiving node; record the digital asset in a database; and coordinate a transaction associated with the digital asset. [0087] The 150E computer-readable medium may also include code, executable by the 150A processor for the implementation of a method that includes the processing, by a first data center computer, of a first digital asset that indicates the transfer of a value from a sender to a recipient; record the first digital asset in a first database; and send a message to a second data center computer, indicating that the first digital asset has been registered, where the second data center computer updates the second database based on the message.
[0088] The computer-readable medium 150E may also include code, executable by the processor 150A to implement a method that includes the processing, by a first data center computer, of a first data element; create, through the first data center computer, a first record of the first data element in a first database; and send, through the first data center computer, a message to a second data center computer indicating that the first record was created, in which the second data center computer updates a second database based on the message.
[0089] The computer-readable medium 150E may also include code, executable by the 150A processor to implement a method comprising the creation, by the first data center computer, of a first block for a first blockchain, the first block, including a first header block and first block body; and send, through the first data center computer, a message to a second data center computer indicating that the first block was created for the
Petition 870190022368, of 03/08/2019, p. 54/158
28/114 first blockchain, the message including the first block header, but not the first block body, where the second data center computer adds the first block header to a second blockchain and where the second data center computer does not add the first block body to the second blockchain.
[0090] As mentioned above, one or more functions, modules, databases or other aspects of the computer of administrative node 150 can instead be incorporated into the interaction platform 154.
[0091] The 150F enrollment module can include the code that causes the 150A processor to enroll entities (for example, financial institutions, users and companies) to interact with the asset transfer network. For example, the 150F enrollment module may contain logic that causes the 150A processor to receive a request from an entity to join the system. The logic can include instructions for assessing whether an entity can enroll, as well as the level of risk to be assigned to a new entity. For example, the computer of administrative node 150 can determine a risk profile for an enrolling financial institution, based on, for example, whether it is a known bank (for example, based on the name of the financial institution or bank identification number ), the risk level of the bank's country and whether the bank has provided collateral. The computer of administrative node 150 can assign a risk level, as well as activity limits based on the risk profile. Activity limits for various types of entities may include, for example, maximum transaction limit limits and / or speed limits, such as a limit on the number of digital assets or the total value of the digital asset that can be generated within a certain period of time (for example, a day, a week or a month).
[0092] The 150F enrollment module may include instructions for assigning permissions to enrolled entities. For example, the node's computer
Petition 870190022368, of 03/08/2019, p. 55/158
29/114 administrative 150 can allow different nodes, service providers and users to have different views of a global transaction ledger. In some embodiments, the computer at administrative node 150 may allow financial institutions to view the transactions to which they were parties.
[0093] When users and companies sign up to participate in the asset transfer network, their information (for example, a name, an address, a phone number, a corporate business profile, etc.) may be disclosed to the computer of administrative node 150, so that the computer of administrative node 150 has sufficient information about participating entities. In addition, in some embodiments, the computer at administrative node 150 may have access to user information collected by a service provider (for example, a bank), such as a user's legal name, address (street, city, country, etc.), date of birth and any other appropriate information.
[0094] The 150F enrollment module may also include instructions for generating and assigning a corporate ID to an enrolled entity. In addition, there may be instructions for generating and distributing keys to enrolled entities. For example, the computer of administrative node 150 can generate a key pair for a bank or user when enrolled. In some embodiments, the computer of the administrative node 150 can provide a digital certificate to an enrolled entity, the digital certificate proving that the entity is certified by the computer of the administrative node 150 and the digital certificate that links the entity to a public key. In some embodiments, a public key can be used as a corporate ID.
[0095] Information about registered users, companies and other participants can be kept in the 150Q user database. In some embodiments, a separate 150C node database may include
Petition 870190022368, of 03/08/2019, p. 56/158
11/30 information about other nodes (for example, sending nodes and recipient nodes), as well as entities associated with those nodes.
[0096] The 150G verification module can include code that causes the 150A processor to verify a digital signature. For example, the 150G verification module may contain logic that causes the 150A processor to apply a public key to a digital signature in order to verify that the signature is authentic. For example, if a signed digital asset is supposed to be generated by the computer of the sender node 165, a public key associated with the computer of the sender node 165 can be used to verify the signature.
[0097] The 150H risk module may include code that causes the 150A processor to assess transaction risk and / or entity risk. For example, the 150H risk module may contain logic that makes the 150A processor determine the risk of a particular digital asset based on the transaction speed of one or more parties involved.
[0098] The 150H risk module may also include instructions to place restrictions on entities that are showing risky behavior or entities involved in settlement failure. For example, if a financial institution exceeds spending limits, the computer of administrative node 150 may temporarily block digital assets generated by the financial institution.
[0099] The 150J validation module can include code that makes the 150A processor validate a transaction. For example, the 150J validation module may contain logic that causes the 150A processor to analyze information on a digital asset and determine whether or not to approve the digital asset. For example, instructions may include determining whether the named recipient (and / or sender) of a digital asset is an enrolled customer who has been verified for compliance. Instructions may also include verifying that financial institutions (or other providers
Petition 870190022368, of 03/08/2019, p. 57/158
31/114 of services) are complying with rules and protocols. For example, financial institutions may be required to have Meet-Your-Consumer compliance (for example, sufficient information about users), Foreign Asset Control Compliance Office, anti-money laundering compliance, etc. In addition, in some modalities, a final transaction amount and currency can be confirmed based on the shipping amount and currency, the exchange rate and transfer fees. [00100] The 150K signature module can include code that causes the 150A processor to generate digital signatures. For example, the 150K signature module may contain logic that causes the 150A processor to generate a digital signature for a digital asset using an administrative node private key. The digital signature of the administrative node's computer can serve to indicate the authenticity of a digital asset and can provide assurance that a transfer is valid and reliable. In some modalities, the digital signature of the administrative node's computer can be considered a co-distribution of the digital asset or a minting of the digital asset. In addition, the digital signature can generate and / or activate a smart contract that holds the computer of the sending institution 160 responsible for the quantity of sending in the currency of origin. For example, a smart contract can automatically start a settlement process after a certain period of time. In some embodiments, the computer of administrative node 150 may force settlement between a sending institution account and a receiving institution account at a central bank.
[00101] In some embodiments, the computer of administrative node 150 may include or be associated with a hardware security module (shown in FIG. 2 as the key database 150P). The hardware security module (HSM) can store one or more keys (for example, a private key) for the computer of administrative node 150 and the hardware security module can sign messages and / or digital assets
Petition 870190022368, of 03/08/2019, p. 58/158
32/114 on behalf of the issuing node 165 computer.
[00102] The 150L ledger update module can include code that causes the 150A processor to maintain a transaction ledger. For example, the 150L ledger update module may contain logic that causes the 150A processor to record information about a digital asset along with previous digital asset records. For example, the computer of administrative node 150 can record a digital asset once it is minted (for example, digitally approved and signed) and / or once it is sent to the computer of recipient node 145. The ledger can be certified as authentic by the computer of administrative node 150 and authenticity can be shown by a digital signature (for example, for each transaction or for the entire ledger).
[00103] In some embodiments, the 150L ledger update module may include instructions for maintaining a transaction ledger in the form of a blockchain. For example, the computer of administrative node 150 may be able to create and / or sign new blocks. A new block that includes one or more digital assets can be generated after an average time interval (for example, every 1 second, 5 seconds, 10 seconds, 30 seconds, 1 minute, ten minutes, 1 hour, etc.). Authenticity can be provided to a block via a digital signature. The administrative node computer 150 can optionally create a hash header for each block based on the digital assets in the block body, a hash from a previous block, a block identifier or transaction identifier, a nonce, a random number and / or any other appropriate information.
[00104] An accounting book, like a blockchain accounting book, can be stored in a 150D accounting book database. Additional databases can store
Petition 870190022368, of 03/08/2019, p. 59/158
33/114 transaction records (for example, a list of transactions not on a blockchain) and / or invoice records. In addition, a settlement database can include information about the transactions to be settled. In some embodiments, one or more of these databases may instead be incorporated by the transaction repository 156.
[00105] In modalities of the invention, the blockchain ledger may not be present on all computers in a distributed network, but it can be maintained by a computer from the secure administrative node 150. Consequently, computationally intensive resources, such as evidence of may not be present or necessary. In some embodiments, there may be multiple administrative node computers 150 that each receive transaction updates and update their own ledger. These different administrative node computers 150 can communicate with each other to confirm that their ledgers have the same transaction information.
[00106] The 150L ledger update module can include instructions for providing transaction updates to other nodes. For example, when a new digital asset is validated and signed, the computer of administrative node 150 can distribute information about the new digital asset to other nodes (other administrative nodes, sending nodes and / or recipient nodes) on the network, so that others we can update their own accounting books. The computer of administrative node 150 can additionally or alternatively distribute information about accounting book updates (for example, new transaction blocks).
[00107] In some embodiments, issuing nodes and receiving nodes cannot maintain their own accounting book and, instead, they can refer to the centrally maintained accounting book of the administrative node computer 150. For example, the computer of the issuing node 165 and the computer of the recipient node 145 can be light nodes. In this case, the
Petition 870190022368, of 03/08/2019, p. 60/158
34/114 administrative node computer 150 can provide other nodes with real-time access to a central ledger, or administrative node computer 150 can provide regular ledger updates (for example, updates can be sent every 10 seconds, 1 minute, 5 minutes, etc.). As a result, other nodes may be aware of new digital assets immediately or shortly after digital assets are minted.
[00108] The transaction accounting book can provide administrative node 150 with real-time visibility of the net position of each financial institution, user and / or company at any time. However, in some embodiments, other entities may not be able to see the entire ledger and, instead, may have a filtered or allowed view of the ledger. For example, other nodes, financial institutions and / or users may only be able to view the transactions to which they were a party.
[00109] This selective disclosure of confidential information in the global accounting book can be carried out using one or more techniques. For example, the administrative node computer 150 may not provide other nodes (for example, the sender node computer 165 and / or the recipient node computer 145) with access to the complete ledger. Instead, the computer of administrative node 150 can only allow each node to display transactions in the ledger with which it is associated (for example, based on a corporate ID, encryption key, transaction ID, etc.). For example, the computer of administrative node 150 can send a reduced copy of the ledger to each node or can block parts of the ledger when a central ledger is being accessed by a node. In some embodiments, information about some recorded transactions may be obscured (for example, encrypted) in the block body or removed from the block, but all
Petition 870190022368, of 03/08/2019, p. 61/158
35/114 block headers can still be provided. As a result, the entire blockchain (which can be linked by hash headers) can still be shown as complete, but the transaction details within blocks can be removed or obscured.
[00110] In some modalities, single-use addresses (for example, single-use company IDs or other single-use identifiers) can be used for beneficiaries and / or payers. As a result, the user and / or the resource provider may not be personally identifiable based on an address or other information on a digital asset. Thus, even if a transaction (and the details of the transaction) are publicly visible, the user may not be identified based on the information in the transaction. Instead, the user's identity and account number may remain anonymous. However, the user and the resource can maintain information about single-use addresses and identifiers they have used, and therefore be able to identify the transactions in the ledger to which they were a party.
[00111] In some modalities, a filtered ledger view can also be achieved by encrypting metadata on digital assets. For example, information that identifies the user and / or the resource provider on a digital asset can be encrypted with public keys associated with the user and / or resource provider. As a result, only the user and / or the resource provider may be able to decrypt and display identifying (or other) information on digital assets included in an accounting book to which they were a part.
[00112] In some modalities, zero knowledge tests can be used to verify the authenticity of a filtered transaction ledger. When the value of the digital asset and / or identification information in a transaction is cryptographically hidden, a
Petition 870190022368, of 03/08/2019, p. 62/158
36/114 Proof of zero knowledge can be used to validate the integrity of the content. For example, an external party may use a zero proof of knowledge to verify that the claimed value of a digital asset is authentic (and not fraudulent), or to verify that a blockchain ledger is authentic, but the external party may not be able to identify the exact history of the value or the parties involved. As a result, only the parties involved (and those granted access) can view the details of the transaction. The modalities may not require normal proof of work, as the accounting book can be trusted without such verification (for example, due to the federated nature of the network).
[00113] The 150L ledger update module can include instructions for communicating information about new digital assets to end users (for example, user computer 110 and / or resource provider computer 130). For example, the computer of administrative node 150 can send a message to the user's computer and / or the resource provider's computer 130 when a digital asset is created, signed and / or distributed. As a result, end users may be aware of new transfers when they occur initially. In some embodiments, messages can instead be sent to service providers (for example, the sending institution's computer 160 and / or the receiving institution's computer 140), which can in turn inform users final.
[00114] As mentioned above, in some embodiments, the computer of administrative node 150 (or interaction platform 154) can perform one or more functions in place of the computer of the sending node 165. For example, instead of the computer of the sending node 165, the computer of the administrative node 150 can generate digital assets on behalf of the computer of the sending institution 160. For this reason, the computer of the administrative node 150 can include a 150M digital asset module. The assets module
Petition 870190022368, of 03/08/2019, p. 63/158
37/114 digital 150M can include code that causes the 150A processor to create digital assets. For example, the 150M digital asset module may contain logic that causes the 150A processor to generate a digital asset, including information associated with transferring a value from a user account to a recipient account.
[00115] In addition, in some embodiments, the computer of the administrative node 150 can generate a digital signature on behalf of the computer of the sending institution 160 and / or the computer of the sending node 165. For example, the computer of the administrative node 150 can store the keys associated with the sending institution's computer 160 and / or the issuing node's computer 165 and can create a digital signature for a digital asset after the digital asset is generated.
[00116] Referring back to FIG. 1, the computer of the sending node 165 can be a node in the asset transfer network and the computer of the sending node 165 can be associated with the computer of the sending institution 160. The computer of the sending node 165 may be able to generate, coin ( or request creation) and / or provide digital assets in order to transfer value (for example, funds) on behalf of the sending institution's computer 160. In some embodiments, the issuing node 165's computer may receive a payment instruction from computer of the sending institution 160 through the interaction platform 154.
[00117] In some modalities, the computer of the issuing node 165 can provide services exclusively to a financial institution. In other embodiments, the computer of the issuing node 165 may represent two or more financial institutions (for example, several banks).
[00118] In some embodiments, the computer of the issuing node 165 may be enrolled centrally (for example, by the computer of the administrative node 150 or a third-party subscription service provider) in order to participate in the asset transfer network. Once enrolled, the
Petition 870190022368, of 03/08/2019, p. 64/158
38/114 sender node 165 computer can be associated with a corporate ID. [00119] An example of an emitter node computer 165, according to some embodiments of the invention, is shown in FIG 3. The emitter node computer 165 comprises a processor 165A, a network interface 165B, a database 165C accounting and a 165D computer-readable medium.
[00120] The 165 D computer-readable medium may include a 165E interaction module, a 165F digital assets module, a 165G subscription module, a 165H approval module, a 165J distribution module, a book update module 165K accounting and any other suitable software module. The 165F computer-readable medium may also include code, executable by the 165A processor to implement a method that comprises receiving a request to transfer a value from a sender associated with a sender identifier to a recipient associated with a recipient identifier; generate a digital asset indicating that the amount is being transferred to the recipient; generate a first digital signature for the digital asset, the first digital signature generated with a first private key associated with the issuing node's computer; send, to a computer of the administrative node, a request to validate the digital asset, the request including the digital asset and the first digital signature, in which the computer of the administrative node validates the digital asset and generates a second digital signature for the digital asset , the second digital signature generated with a second private key associated with the administrative node's computer; receive the second digital signature from the administrative node's computer; and supplying the digital asset to a recipient node computer associated with the recipient, where the administrative node computer registers the digital asset in a database and coordinates a transaction associated with the digital asset.
Petition 870190022368, of 03/08/2019, p. 65/158
39/114 [00121] The 165E interaction module can include code that causes the 165A processor to interact with other entities, such as the sending institution's computer 160 and the interaction platform 154. For example, the 165E interaction module it may contain logic that causes processor 165A to receive a payment instruction from the sending institution's computer 160 (for example, through interaction platform 154).
[00122] The 165F digital assets module can include code that causes the 165A processor to create digital assets. For example, the 165F digital asset module may contain logic that causes the 165A processor to generate a digital asset, including information for transferring a value from a user account to a recipient account.
[00123] The 165G signature module can include code that causes the 165A processor to create a digital signature. For example, the 165G signature module may contain logic that causes the 165A processor to apply a private key and / or a mathematical algorithm to a digital asset, so that the digital signature is generated for the digital asset. Other entities (for example, other nodes) may then be able to use a corresponding public key to verify the digital signature and, thus, verify the authenticity of the digital asset.
[00124] In some embodiments, the computer of the emitting node 165 may include or be associated with a hardware security module. The hardware security module (HSM) can store one or more keys (for example, a private key) for the computer of the issuing node 165 and the hardware security module can sign messages and / or digital assets on behalf of the computer of the emitter node 165.
[00125] In some embodiments, the key pair of the computer of the issuing node can be generated and provided by the computer of the administrative node 150 (for example, through a digital certificate) or by a computer
Petition 870190022368, of 03/08/2019, p. 66/158
40/114 separate third party service. In other embodiments, the computer key pair of the issuing node can be generated locally (for example, by a hardware security module). When a key pair is generated locally, the issuing node computer 165 can supply the key pair to the administrative node computer 150 during enrollment.
[00126] The 165H DE approval module can include code that causes the 165A processor to obtain approval for a digital asset. For example, the 165H DE approval module may contain logic that causes the 165A processor to provide a digital asset and / or a digital signature from the issuing node corresponding to the computer of administrative node 150 to obtain approval and a second digital signature from the computer of the administrative node 150. The computer of administrative node 150 can then verify the digital signature of the computer of the issuing node, validate the digital asset and generate a second digital signature for the digital asset.
[00127] The 165J distribution module can include code that causes the 165A processor to distribute digital assets. For example, distribution module 165J may contain logic that causes processor 165A to supply a digital asset to a computer of recipient node 145, a computer of administrative node 150 and / or any other suitable node or other entity. To provide a digital asset to the computer of the appropriate recipient node 145, the computer of the sending node 165 can operate appropriate routing tables. For example, the computer of the recipient node 145 can be identified based on a corporate identifier, public key, bank identification number and / or any other appropriate identifier in the digital asset.
[00128] The 165K ledger update module can include code that causes the 165A processor to record information related to the creation and / or distribution of a digital asset for a transaction. For example, the ledger update module
Petition 870190022368, of 03/08/2019, p. 67/158
41/114
165K may contain logic that causes the 165A processor to record information by updating a transaction ledger based on a new digital asset or other transaction. This ledger can be stored in the 165C ledger database. The 165K ledger update module may include instructions for adding a block to a blockchain, the new block including information about one or more transactions.
[00129] In some embodiments, the computer of the issuing node 165 may display an accounting book maintained by the computer of the administrative node 150 or by a third party accounting book manager, instead of maintaining its own accounting book.
[00130] In some modalities, the computer of the issuing node 165 can only display a subset of transactions that take place within the asset transfer network. For example, the computer of the issuing node 165 may have a filtered view of a complete ledger (for example, a blockchain) maintained by the computer of the administrative node 150. The computer of the issuing node 165 may be able to display transaction records for transactions to which the sender node 165 computer or the sending institution computer 160 was a party. In some embodiments, the sender node 165 computer may be able to display the block headers for each block in the total blockchain, but the sender node 165 computer may not be able to display some or all of the registration information within the bodies of block (for example, transactions with which the computer of the issuing node 165 is not associated, or transactions that occurred in a different country).
[00131] This filtered accounting book view can be achieved through several possible implementations. For example, the computer of the emitting node 165 may be a light node, only receiving information about relevant transactions. In an implementation, the sender node's computer
Petition 870190022368, of 03/08/2019, p. 68/158
42/114
165 only receives all block headers, but only receives the corresponding block bodies for transactions with which it is associated. If the computer of the issuing node 165 builds its own copy of the transaction ledger, it can only receive block headers for some blocks. If the computer of the issuing node 165 does not build its own accounting book and instead accesses a central accounting book (for example, maintained by the computer of the administrative node 150), the central accounting book can be filtered when the computer of the sender node 165 to access it, so that the sender node 165 computer can only see the block headers for certain blocks.
[00132] In some embodiments, the computer of the issuing node 165 may obscure or remove parts of the accounting book by showing it to the computer of the sending institution 160. For example, the computer of the issuing node 165 may have access to the entire book accounting, but you can remove block bodies for some blocks (while still optionally displaying block headers) when the sending institution's computer 160 views the accounting book.
[00133] Additional techniques for providing filtered accounting book view are described above. For example, digital assets may include less information about supplying entities (for example, the user, the sending bank and / or the sending node), so that recipients can receive the value of the digital asset without sender's personal information is exposed.
[00134] In some embodiments, one or more of the computer functions of the sender node described above 165 may, instead, be performed by another entity, such as the computer of administrative node 150 or interaction platform 154. For example, instead from the computer of the sending node 165, the interaction platform 154 can generate a digital asset on behalf of the computer of the sending institution 160 (for example, the platform
Petition 870190022368, of 03/08/2019, p. 69/158
43/114 of interaction 154 can do this instead of forwarding a transaction instruction to the computer of the issuing node 165). Likewise, in some embodiments, another entity can manage keys and provide digital signatures on behalf of the issuing node computer 165. For example, the administrative node computer 150 or interaction platform 154 can store the keys of the issuing node computer in an HSM and can generate digital signatures for digital assets on behalf of the issuing node 165 computer.
[00135] Referring back to FIG. 1, the computer of recipient node 145 may be a node in the asset transfer network. The computer of the recipient node 145 can be associated with or operated by the computer of the receiving institution 140. For example, the computer of the receiving node 145 may be able to receive digital assets on behalf of the computer of the receiving institution 140, it can store digital assets on behalf of the receiving institution. computer of the receiving institution 140 and can transfer the digital assets received to the computer of the receiving institution 140 (for example, through the interaction platform 154).
[00136] In some modalities, the computer of the recipient node 145 can provide services exclusively to a financial institution. In other embodiments, the computer of the recipient node 145 may represent two or more financial institutions (for example, several banks).
[00137] The computer of recipient node 145 can be enrolled centrally (for example, by the computer of administrative node 150) in order to participate in the asset transfer network. Once enrolled, the computer of recipient node 145 can be associated with a corporate ID.
[00138] The computer of the recipient node 145 may be able to receive a digital asset sent by the computer of the sending node 165 and / or the
Petition 870190022368, of 03/08/2019, p. 70/158
44/114 administrative node computer 150. In some embodiments, digital assets can be transmitted to several or all nodes and the recipient node computer 145 can identify which digital assets are relevant to the receiving institution and / or service provider resources (for example, based on a recipient corporate ID indicated on the digital asset).
[00139] The computer of the recipient node 145 can also validate that a digital asset is authentic. For example, the computer of recipient node 145 can verify one or more digital signatures associated with a digital asset. Digital signatures can be verified with the public keys associated with the signature entities (for example, the sending institution computer 160, the issuing node computer 165e / or the administrative node computer 150).
[00140] In some modalities, the computer of recipient node 145 can also record information about the digital assets received for a transaction. For example, the computer of recipient node 145 can update a transaction ledger based on a new digital asset or other transaction. In some embodiments, the recipient node 145's computer can add a block to a blockchain, the new block including information about one or more digital assets. In other embodiments, the computer of the recipient node 145 can display an accounting book maintained by the computer of the administrative node 150, instead of maintaining its own accounting book.
[00141] In some modalities, the computer of recipient node 145 will only be able to display a subset of transactions that occur within the asset transfer network. For example, the computer of recipient node 145 may have a filtered view of a complete ledger (for example, a blockchain) maintained by the computer of administrative node 150. The computer of recipient node 145 may be able to display transaction records for the transactions to which the node's computer
Petition 870190022368, of 03/08/2019, p. 71/158
45/114 recipient 145 or the computer of the receiving institution 140 was part. For example, the computer of recipient node 145 may be a light node, only receiving information about relevant transactions. In some embodiments, the computer of recipient node 145 may be able to display the block headers for each block in the total blockchain, but the computer of recipient node 145 may not be able to display some or all of the registration information within the bodies of block. For example, block bodies can be removed that include transactions that the recipient node 145 computer is not associated with or transactions that occurred in a different country.
[00142] In some embodiments, if the computer of recipient node 145 builds its own copy of the transaction ledger, the computer of administrative node 150 can only send block headers for some blocks when the computer of administrative node 150 provides updates of the accounting book for recipient node computer 145. Alternatively, if the recipient node computer 145 does not build its own accounting book and instead accesses a central accounting book (for example, maintained by the administrative node computer 150), the central ledger can be filtered when it is accessed by the computer of the recipient node 145, so that the computer of the recipient node 145 can only see the block headers for certain blocks (for example, blocks, including digital assets with which the computer of recipient node 145 is associated with).
[00143] In some embodiments, the computer of the recipient node 145 can remove the information from the accounting book when the computer of the receiving institution 140 is viewing the accounting book. For example, the computer of recipient node 145 may obscure or reduce the ledger (for example, by encrypting or removing some transaction details and / or block bodies for
Petition 870190022368, of 03/08/2019, p. 72/158
46/114 some transactions, but still showing the block headers), so that the computer view of the institution receiving the accounting book is filtered.
[00144] The computer of the issuing node 165 and the computer of the receiving node 145 can provide different services (for example, supply and receipt of digital assets) to a financial institution that uses the asset transfer network. Consequently, each financial institution (for example, the sending institution's computer 160 and the receiving institution's computer 140) can use the services of a computer from the sending node 165 and a computer from the receiving node 145. In some embodiments, a single node it can act as a sending node and a receiving node.
[00145] The receiving institution's computer 140 can store value and receive value (for example, receiving a payment) on behalf of the resource provider's computer 130. An example of a receiving institution can be an acquirer, which can typically be an entity commercial (for example, a commercial bank) that has a business relationship with a specific resource provider or other entity. Some entities can perform both issuer and acquirer functions. Some modalities may cover such single acquiring issuing entities.
[00146] In some modalities, the computer of the receiving institution 140 can make a value indicated in a digital asset received immediately usable (for example, extractable) in a resource provider account. The receiving institution's computer 140 can settle the transaction by receiving the real value from the sending institution's computer 160 (instead of just an IOU) at a later time.
[00147] The computer of the receiving institution 140 can register for interaction with the asset transfer network (for example, through the
Petition 870190022368, of 03/08/2019, p. 73/158
47/114 interaction platform 154 or the computer of the administrative node 150), in order to participate in system 100. As a result, the computer of the receiving institution 140 can receive and be associated with a unique corporate ID. In some embodiments, the computer of the receiving institution 140 can also receive and be associated with a key pair. This key pair can be stored in an HSM.
[00148] The resource provider's computer 130 can be associated with a resource provider, which can be an entity that can provide a resource, such as goods, services, information and / or access. Examples of a resource provider include merchants, access devices, secure data access points, etc. A trader can normally be an entity that engages in transactions and can sell goods or services or provide access to goods or services.
[00149] The resource provider can have an account on the computer of the receiving institution 140. The account can be associated with various information from the resource provider. For example, a resource provider account can be associated with a business name, a home and / or business address, a phone number, an account user name, an account password, an email address, etc. .
[00150] Resource provider computer 130 can be enrolled for asset transfer network services. For example, the resource provider can enroll through the interaction platform 154 or the receiving institution's computer 140 can enroll on behalf of the resource provider. Consequently, the resource provider's computer 130 can also be associated with a unique corporate ID. [00151] In some embodiments, the resource provider's computer 130 may have relationships with several institutions (for example, a receiving institution and a sending institution). Resource provider computer 130 can register with the asset transfer network via
Petition 870190022368, of 03/08/2019, p. 74/158
48/114 through each entity and, thus, can associate with several corporate IDs. For example, a first corporate ID can represent the resource provider's computer 130 when interacting through a receiving institution and a second corporate ID can represent the resource provider's computer 130 when interacting with the network through a sending institution. In some embodiments, different company IDs can be assigned to the resource provider's computer 130 for the transaction (for example, creation of digital assets) in different types of currency (for example, a first corporate ID for US dollars and a second identification British pounds). The modalities allow the user and any other suitable entity to obtain multiple corporate IDs in a similar way.
[00152] The foreign exchange transaction application interface 152 can provide information on exchange rates. For example, before initiating an international transaction, the user's computer 110 and / or the sending institution's computer 160 may be able to view real-time exchange rates for the transaction. In some embodiments, the foreign exchange transaction application interface 152 may be provided by the interaction platform 154, the administrative node computer 150 or otherwise by a management entity (for example, a payment processing entity).
[00153] The settlement service computer 155 (which may include one or more server computers) may be able to provide settlement services. For example, a digital asset can act as a payment guarantee or an IOU (for example, an intended payment certificate), but the actual transfer of funds cannot actually occur when a digital asset is provided. Thus, after the digital asset is sent, the settlement service computer 155 may be able to facilitate the effective exchange of funds between the sending institution's computer
Petition 870190022368, of 03/08/2019, p. 75/158
11/4
160 and the receiving institution's computer 140 (for example, transferring value between the respective settlement accounts at a central settlement bank). The settlement service computer 155 can facilitate settlement by interacting with a central settlement account service (for example, a central bank) that can be associated with the asset transfer network. For example, a central bank can be associated with the computer of the administrative node 150, the interaction platform 154 or a generation entity. In some embodiments, the settlement service computer 155 may be operated by the interaction platform 154 or otherwise by a management entity (for example, a payment processing entity).
[00154] Transaction repository 156 (which may include one or more server computers) can be a database for past transactions. For example, a transaction ledger can be stored in the transaction repository 156. The administrative node computer 150 can store its ledger book (for example, a blockchain ledger) or a non-blockchain transaction record in the repository of transactions 156.
[00155] The risk management computer 157 (which may include one or more server computers) can provide risk management services. For example, the risk management computer 157 can analyze the risk associated with digital assets being sent on the asset transfer network. In some embodiments, the functions described in relation to the risk module 150H on the computer of the administrative node 150 can, instead, be performed by the risk management computer 157.
[00156] In some modalities, system 100 may include one or more asset auditing nodes (not shown), which may be able to audit the network. For example, an asset auditor node can confirm that
Petition 870190022368, of 03/08/2019, p. 76/158
50/114 different accounting books correspond, that we and financial institutions are acting within the rules and limits, and that no double expenses are occurring. The asset auditing nodes can be operated by the same management entity as the interaction platform 154 and / or the computer of the administrative node 150.
[00157] As mentioned above, system 100 can be used for any type of value transfer, such as transferring access credentials, digital media or any other suitable value. Consequently, service providers that are not financial institutions may also be able to participate in system 100. For example, other service providers may be able to manage user accounts, operate sending and receiving nodes, etc.
[00158] An example of an asset transfer network is shown in FIG. 4. In some embodiments, as shown in FIG. 4, several of the nodes may be able to deliver and receive digital assets within the asset transfer network. An example transfer is shown, in which a computer from sender node 165 is delivering a digital asset to a computer from recipient node 145. As long as a forward arrow is shown, the computer from sender node 165 can actually transmit digital asset information to multiple or all nodes in the network. One or more administrative nodes can maintain an accounting book for digital assets that have been transferred between us.
[00159] In some modalities, the asset transfer network can be a blockchain network. For example, the ledger may take the form of a blockchain. Each block on the blockchain can include information about one or more transactions (for example, digital assets). A blockchain ledger can be unchanged without detection. For example, each block can include a data header that includes a hash of the previous block in the blockchain ledger and a root value of
Petition 870190022368, of 03/08/2019, p. 77/158
51/114 all past transactions. Since each block in the blockchain ledger can be generated in a similar way by including a data header that stores information regarding previous entries and transactions, no entry can be modified without affecting all subsequent entries. This ensures that any manipulation of information in relation to transactions, such as an attempt to reassign a digital asset to an inappropriate entity, does not go unnoticed. Together, a block header and a block body that includes the transaction information (for example and any other suitable information) can make a block.
[00160] As mentioned above, a blockchain can be a distributed database that maintains a continuously growing list of digital records protected from tampering and review. A blockchain can include a number of blocks of interaction records. Each block on the blockchain can also contain a timestamp and a link to a previous block. For example, each block can include or be added to a hash of the previous block. In other words, interaction records on a blockchain can be stored as a series of blocks or permanent files that include a record of a series of transactions that take place over a given period of time. Blocks can be added to a blockchain through an appropriate node after the block has been completed and the block is validated. In embodiments of the invention, a blockchain can be distributed and a copy of the blockchain can be kept on each node in a verification network. Any node within the verification network can subsequently use the blockchain to verify transactions. The security of a blockchain can be achieved using a cryptographic scheme.
[00161] In some embodiments, the asset transfer network can be a federated asset transfer network (also known as an allowed asset transfer network). For example,
Petition 870190022368, of 03/08/2019, p. 78/158
52/114 permission may be required from a central trusted party to be able to participate in the asset transfer network. As explained above, the computer of administrative node 150 may be able to register entities on the network. Thus, the computer of administrative node 150 may be able to decide which parties can participate, as well as define rules and protocols for participating in the network. The computer of administrative node 150 may also be able to restrict an entity, if desired (for example, to limit or block a financial institution due to bad behavior). [00162] The entities that can validate the network (for example, enroll entities to participate and enforce compliance) can be referred to as federated entities. In some embodiments, the computer of administrative node 150 may be the only federated entity. In other embodiments, another entity may perform this administrative function instead of the computer at administrative node 150. For example, a management entity (which may be associated with the computer at administrative node 150) or a separate third-party service provider may administer the asset transfer network.
[00163] In some modalities, the asset transfer network can function as a private asset transfer network. For example, the asset transfer network can serve as a tool for a transaction processor to record transactions. The network ledger can essentially be a third party record keeping system and can only be accessed and / or modified by the transaction processor.
[00164] A method 500 according to the modalities of the invention can be described with reference to FIG. 5. Some elements in other figures are also mentioned. The steps shown in method 500 can be performed sequentially or in any order appropriate to the modalities of the invention. In some modalities, one or more of the steps can be
Petition 870190022368, of 03/08/2019, p. 79/158
53/114 optional.
[00165] The various messages described below can use any suitable form of communication. In some embodiments, a request or response may be in an electronic message format, such as an email, a short message service (SMS) message, a multimedia message service (MMS) message, a protocol request message. hypertext transfer (HTTP), a transmission control protocol (TCP) package, a web submission form. The request or response can be directed to any appropriate location, such as an email address, a phone number, an Internet Protocol (IP) address, or a uniform resource locator (URL). In some embodiments, a request or response may comprise a mixture of different types of messages, such as e-mail and SMS messages.
[00166] As described above, a number of entities can be enrolled for interaction with an asset transfer network (which can be a blockchain network). Each entity (for example, nodes, financial institutions and users) can be associated and identifiable based on a unique corporate ID. In the following example, the network is used to transfer currency. However, the transfer of any other appropriate type of value (for example, usage credit, access credentials, ownership credentials, digital media, etc.) may also occur.
[00167] User 510's computer can start by providing a value to the 530 resource provider's computer. For example, the resource provider can provide goods or services to the user and the 530 resource provider's computer can send a payment invoice to the user's computer 510. The invoice can include a quantity, a currency type, a corporate ID associated with the resource provider's 530 computer, or a resource provider account,
Petition 870190022368, of 03/08/2019, p. 80/158
54/114 information about goods or services provided, an invoice identifier and any other appropriate information.
[00168] In step S502, the user (for example, through the user's computer 510) can contact the sending institution's computer 560 and request that a payment is sent to the resource provider's computer 530. The user's computer 510 can provide any appropriate payment information, such as a recipient amount and currency type, information that identifies the recipient (for example, the resource provider's corporate ID), an invoice, and a selection of a user account to withdraw from funds for payment.
[00169] Payment can be an international transfer. For illustrative purposes only, the user account may be a United States-based account, including U.S. dollars. The recipient account (for example, the resource provider) can be an account based in England, including British pounds.
[00170] In step S504, the sending institution's computer 560 can collect information to initiate payment. For example, for an international transaction, a foreign exchange rate may be required to identify the correct amount of currency to be withdrawn from the user's account. The computer of the sending institution 560 can obtain information about a current exchange rate relevant to the transaction (for example, exchange rate from US dollars to British pounds) from the foreign exchange application interface (for example, through the interaction platform ).
[00171] The exchange transaction application interface or interaction platform can also provide information on transfer fees that may be charged for the transaction. For example, there may be fees charged by the sending institution's computer 560, the receiving institution's computer 540e / or any of the nodes
Petition 870190022368, of 03/08/2019, p. 81/158
55/114 participants to manage the transaction. In some embodiments, all of these fees can be immediately calculated and available before the transaction is initiated. The sending institution's computer 560 can also provide this fee and foreign exchange information to user 510's computer.
[00172] Consequently, the sending institution's computer 560 may be able to determine the amount of funds that will be withdrawn from the user's account (that is, how much to charge the user). The total charge can be calculated based on the amount the resource provider must receive, the transfer fees and the exchange rate.
[00173] For example, the user may wish to provide £ 1000 to the resource provider. The exchange rate can be 1 Pound Sterling to 1.33 US Dollars. Consequently, $ 1330 may be required to provide £ 1000. Additionally, the sending institution's 560 computer may charge $ 15 for the transfer. Thus, it can be determined that the user will be charged $ 1345 in order to provide £ 1000.
[00174] In other modalities, the sending institution's computer 560 can, instead, start with the amount indicated by the user to send the currency of origin and can deduct the fees and the exchange rate to determine the amount that the provider of resources you will receive.
[00175] The computer of the sending institution 560 can also check whether the transaction will comply with the rules and limits placed on the user and / or on the computer of the sending institution 560, as well as carrying out any appropriate risk analysis. For example, the sending institution's 560 computer can verify that the transaction will not exceed the speed or quantity limits for the user account or the sending institution's 560 computer. The sending institution's 560 computer can also verify that the account user has sufficient funds for the transaction.
Petition 870190022368, of 03/08/2019, p. 82/158
56/114 [00176] In step S506, the sending institution's computer 560 can send a transaction request to the issuing node's computer 565 (for example, through the interaction platform). The request may include information to provide a payment to the resource provider, such as information about the source currency, the target currency, the amount, rates and exchange rate, a corporate ID of the resource provider, a corporate ID of the and sending the corporate ID of the sending institution's computer 560 and any other appropriate information.
[00177] The computer of the sending institution 560 can also debit or place a hold on the user's account for the total amount of the charge. Thus, the funds may still be available for settlement at a later time.
[00178] In step S508, the computer of the sender node 565 can generate a digital asset for the requested transaction. The digital asset can include any appropriate information (for example, shipping information) to communicate that a value is being transferred from the user account to a resource provider account. For example, the digital asset can include a digital asset identifier, the type of source currency, the type of destination currency, the value of the sending currency, rates and exchange rate, the value of the destination currency, various user information (e.g., user corporate ID, address, phone number, email address), various information from the sending institution's 560 computer (e.g., financial institution name, corporate ID, public key, BIN) , various information from the 530 resource provider's computer (for example, corporate ID, name, address, phone number, email address), various information from the receiving institution's 540 computer (for example, financial institution name, ID corporate key, public key, BIN), a corporate ID and / or computer public key of the issuing node 565, a corporate ID and / or computer public key of the recipient node 545, a
Petition 870190022368, of 03/08/2019, p. 83/158
57/114 invoice number and invoice information, a purchase order number, a time stamp and any other appropriate information. The digital asset identifier can be an identifier generated by the computer of the emitting node 565 that uniquely identifies the digital asset. For example, the digital asset identifier can be a sequence of alphanumeric characters or a scanned image (for example, QR code). A transaction identifier can be used as a digital asset identifier.
[00179] The sender node 565 computer can also generate a digital signature for the digital asset, the digital signature demonstrating that the digital asset was actually created by the sender node 565 computer. The digital signature can be generated by applying a mathematical algorithm the digital asset and the private key of the issuing node's computer (or the private key of the issuing institution's computer). The digital signature can be attached or included in the digital asset, just as the corresponding public key of the issuing node's computer can verify the digital signature.
[00180] The digital asset can be considered a guarantee for the payment amount. Thus, once it is signed and sent, several entities can count the payment as completed or close to completion. For example, the digital asset can be valued in a similar way to a paper check and can include any information needed to obtain the promised funds.
[00181] Before generating and / or providing the digital asset, the computer of the issuing node 565 can also verify that the digital asset transaction is in accordance with rules, protocols and limits (for example, speed limits and transaction value) .
[00182] In step S510, the computer of the emitting node 565 can provide the digital asset and any other information suitable for a computer
Petition 870190022368, of 03/08/2019, p. 84/158
58/114 of administrative node 550. The computer of issuing node 565 can request approval of the digital asset, as well as request a second digital signature. For example, the computer of the sender node 565 may transmit a message that is recognizable by the computer of the administrative node 550 as a transfer request message for digital assets. The message can include the digital asset and the first digital signature and can request that the computer of administrative node 550 approve (for example, validate) the digital asset, provide a second digital signature, post the digital asset in a blockchain ledger , inform the computer of the recipient node 545 about the digital asset and / or otherwise process the digital asset.
[00183] In step S512, the computer of administrative node 550 can validate the digital asset. For example, the administrative node 550 computer can identify each entity involved based on corporate IDs and can ensure that each entity is enrolled and in good standing. For example, the computer of administrative node 550 can verify that each entity is following rules and protocols and within any risk limits. The computer at administrative node 550 can also perform risk analysis on the transaction, checking for any warning flags (for example, an exceptionally high amount or an unusual direction of transfer to a particular account or financial institution).
[00184] The computer of the administrative node 550 can also verify the digital signature of the computer of the sending node (for example, with the public key of the computer of the sending node or the public key of the computer of the sending institution). The computer of administrative node 550 can also verify that the attached public key is actually associated with the corporate ID of the computer of the issuing node and, in the same way, make sure that other information in the digital asset is accurate and valid.
Petition 870190022368, of 03/08/2019, p. 85/158
59/114 [00185] In step S514, after validating the transaction, the computer of administrative node 550 can generate a second digital signature for the digital asset. For example, the computer at administrative node 550 can use a private key to generate a digital signature based on information from the digital asset. In some modalities, the digital asset can be considered coined and valid after the second digital signature is provided.
[00186] In some modalities, the computer of administrative node 550 can also generate a smart contract for the digital asset (for example, a smart contract that indicates under which conditions the value of the digital asset should be settled). For example, each entity participating in the network may, during registration, have agreed to have smart contracts established when a digital asset is requested or generated. Thus, the computer of administrative node 550 may be allowed to create and enforce smart contracts. When a smart contract settlement condition is triggered, the administrative node 550 computer can force settlement between a sending institution account and a receiving institution account (for example, accounts at a central bank or other corresponding accounts).
[00187] In step S516, the computer of the administrative node 550 can supply the digital asset and the second digital signature back to the computer of the issuing node 565. The computer of the issuing node 565 can thus be informed that the digital asset is validated and ready to be used.
[00188] At this point, or at a later time, the computer of administrative node 550 can also update a transaction accounting book based on the digital asset. An entry in the ledger can include information about the amount, the recipient of the amount, the sender of the amount, the date and time of the transaction, the digital asset identifier, and any other appropriate information. In some modalities, the book of
Petition 870190022368, of 03/08/2019, p. 86/158
60/114 accounting may include a copy of the digital asset.
[00189] In some modalities, the computer of administrative node 550 can also distribute information about the digital asset or the updated ledger to other computers of administrative node 550. In addition, when the ledger is updated, the transaction (for example) transfer of user value to the resource provider) can be considered official and guaranteed.
[00190] In some modalities, the computer of administrative node 550 can update an accounting book by adding a new block to a blockchain, the new block including information about the new digital asset. The new block can also include information about other transactions that occurred during a similar period of time (for example, all digital assets minted within a ten-minute interval).
[00191] In some modalities, the accounting book cannot be updated (for example, a block cannot be added) until the transactions are validated throughout the asset transfer network. Network nodes can use Simplified Byzantine Failure Tolerance (SBFT), or any other suitable method, to reach consensus on how blocks are added to the blockchain at each stage. In SBFT, a designated block generator (for example, an administrative node 550 computer) collects and validates the proposed transactions, periodically merging them into a new block proposal. Other designated block signers (for example, computers on administrative node 550) ratify the proposed block with their signatures. All members of the network can know the identities of the block signatories and accept blocks only if signed by a sufficient number of signatories. This ensures that competing transactions can be resolved, transactions can be final and the history cannot be overwritten.
Petition 870190022368, of 03/08/2019, p. 87/158
61/114 [00192] In step S518, having received the second digital signature for the digital asset, the issuing node 565's computer can update a transaction accounting book to include the new digital asset. Alternatively, in some embodiments, the issuing node 565's computer may not maintain its own accounting book and may instead refer to the administrative node's computer accounting book when necessary.
[00193] In step S520, the digital asset can be generated, coined (for example, signed), recorded and ready to send. Thus, in some embodiments, the sender node computer 565 can deliver the digital asset to the recipient node computer 545. The sender node computer 565 can identify the correct recipient node computer 545 to provide the digital asset based on one or plus corporate IDs present in the digital asset (for example, a corporate ID of the computer of the receiving node 545, the computer of the receiving institution 540, or the computer of the resource provider 530). The modalities allow several alternative methods of delivering the digital asset to the computer of the recipient node 545, which are described below after this description of the flow.
[00194] In step S522, the computer of recipient node 545 can receive and verify the authenticity of the digital asset. For example, the computer of the recipient node 545 can verify that one or more digital signatures are authentic and associated with the computer of the sending institution 560, the computer of the sending node 565 and / or the computer of the administrative node 550.
[00195] In some embodiments, the digital asset may include public keys associated with the sending institution's computer 560, the issuing node's computer 565 and / or the computer of the administrative node 550. Alternatively, the digital asset may include associated corporate IDs to one or more of those entities and the recipient node 545 computer can search
Petition 870190022368, of 03/08/2019, p. 88/158
62/114 appropriate public keys based on company IDs. The computer of recipient node 545 can use the included public keys to verify one or more digital signatures.
[00196] In some modalities, verifying the digital signatures can be considered the verification that the information of the digital asset is valid and that the value of the digital asset is legitimately transferred. In some embodiments, the computer of recipient node 545 can also confirm that the amount being transferred is owned correctly by the user (for example, if the computer of recipient node 545 has a complete accounting view or other access to customer account records. user).
[00197] In some modalities, the computer of recipient node 545 can also update an accounting book. Alternatively, in some embodiments, the recipient node 545 computer may not maintain its own accounting book and may instead refer to the administrative node computer's accounting book when necessary.
[00198] In step S524, the computer of recipient node 545 can forward the digital asset to the computer of the receiving institution 540 (for example, through the interaction platform). The computer of the recipient node 545 can supply all digital assets to the same computer of the receiving institution 540 or it can supply the digital asset to a computer of the receiving institution 540, associated with a corporate ID indicated in the digital asset. In addition, the recipient node 545 computer can provide a message to the resource provider 530 computer with information about the digital asset received and the promised value.
[00199] In step S526, the computer of the receiving institution 540 can store the digital asset and associate it with the resource provider account. The computer of the receiving institution 540 can identify the computer of the resource provider 530 and / or the account of the resource provider based on a corporate recipient ID indicated on the digital asset.
Petition 870190022368, of 03/08/2019, p. 89/158
63/114 [00200] In some modalities, the computer of the receiving institution 540 may have a high level of confidence that the authentic digital asset and that the value will be provided. For example, the computer of the receiving institution 540 can trust the digital signatures provided with the digital asset, the computer of the receiving institution 540 can trust the computer of the administrative node 550, and the computer of the receiving institution 540 can trust other participating network entities because they were all selected when registered. It may be unlikely that a fraudster has presented the digital asset instead of the sender's 565 node computer, since the sender's computer's private key can be kept secure. In addition, even if the transfer is initiated fraudulently, the computer of administrative node 550 can still guarantee the funds. In addition, a smart contract that can force the transfer of funds can be established, thus providing a greater guarantee to the computer of the receiving institution 540 that the value indicated in the digital asset will be received.
[00201] Thus, in some modalities, the computer of the receiving institution 540 can immediately credit the account of the resource provider with a value indicated in the digital asset. As a result, the value may be available for use (for example, withdrawn) immediately upon receipt of the digital asset, even if the value is only promised and not actually received. [00202] The amount credited to the resource provider's account may be less than the amount indicated on the digital asset. For example, the computer of the receiving institution 540 and / or other entities may charge fees that can be deducted from the amount provided.
[00203] For example, the resource provider can receive a digital asset for £ 1000 from the user. However, the recipient of the 540 institution's computer may charge £ 20 for the transfer. Consequently, the resource provider's account can only be credited with $ 980.
Petition 870190022368, of 03/08/2019, p. 90/158
64/114 [00204] In step S528, the computer of the receiving institution 540 can inform the computer of the resource provider 530 that a digital asset has been received and that a certain amount has been credited to the resource provider's account. The computer of the receiving institution 540 can provide shipping data, including the payment amount, information about the sender (for example, the user and / or the computer of the sending institution 560) and any other information appropriate to the computer of the provider. 630 resources.
[00205] At this point, the user's computer 510 and / or the sending institution's computer 560 can also be informed that the transfer has been completed. For example, the interaction platform may provide a reconciliation file for the user's computer 510 and / or the sending institution's 560 computer.
[00206] In step S530, at a later time, the settlement of the digital asset value can occur between the sending institution's computer 560 and the receiving institution's computer 540. For example, the settlement service computer can coordinate the transfer of value. Information relevant to settlement (for example, corporate IDs, value, etc.) can be obtained from the digital asset.
[00207] In some embodiments, settlement may include debiting the value of the digital asset from the user's account on the sending institution's computer 560. The value of the digital asset may also be transferred to a central bank (for example, a financial institution provided by an entity that manages the asset transfer network or any other suitable entity). Alternatively, the sending institution 560's computer may have a pre-loaded account with funds at the central bank, so that the value of the digital asset does not need to be transferred from the sending institution 560's computer to the central bank at this point (for example, because the funds are already in the central bank).
Petition 870190022368, of 03/08/2019, p. 91/158
65/114 [00208] Settlement can continue by debiting the value of the digital asset (or an indented settlement amount) from a first account (for example, a first settlement account) associated with the sending institution's computer 560 at the central bank and the amount can be credited to a second account (for example, a second settlement account) associated with the receiving institution's computer 540 at the central bank. For example, the sending institution's computer 560 and the receiving institution's computer 540 may have created the settlement accounts with that central bank when signing up for participation in the asset transfer network, and those accounts may exist specifically for payment procedures. sale off. The first account can be in a central bank's first location, which is in a first country (for example, the United States), while the second account can be in a central bank's second location, which is in a second country (for example, England). Thus, the second account can be credited with British pounds (thus effecting a currency exchange).
[00209] When the amount reaches the second account associated with the computer of the receiving institution 540, the computer of the receiving institution 540 can then credit the account of the resource provider in the receiving institution with the value of the digital asset. Alternatively, as described above, the receiving institution's computer 540 may have already credited the resource provider account in step S526.
[00210] As a result, settlement may not need to travel through multiple corresponding banking relationships. Instead, funds can be settled between the receiving institution's computer 540 and the sending institution's computer 560 through the central bank. In addition, the receiving institution's computer 540 and the sending institution's computer 560 can maintain only one account with the central bank (or other settlement account service provider). The receiving institution's computer 540 and the sending institution's computer 560 may not have to
Petition 870190022368, of 03/08/2019, p. 92/158
66/114 manage any other corresponding banking relationships, since all transfers can be carried out through the asset transfer network and central bank. As a result, the computer of the receiving institution 540 and the computer of the sending institution 560 may not have to reserve resources for several corresponding accounts or otherwise interface with several corresponding banks. In some modalities, each financial institution may maintain several accounts with the central settlement entity in order to carry out transactions in different currencies. For example, the sending institution's 560 computer may have several (for example, 1-20) accounts, each for a different type of currency. As a result, the sending institution's computer 560 can settle transactions with the receiving institution's computer 540 using the best suitable currency. For example, the sending institution's 560 computer can have an account with British Pounds value and can settle directly with the receiving institution's 540 computer using British Pounds.
[00211] In other modalities, the value of the digital asset can be settled through one or more corresponding banking relationships (for example, instead of through a central bank). For example, settlement can take place through one or more correspondent banks in a first country (for example, the United States), an international correspondent bank relationship and one or more correspondent banks in a second country (for example, England).
[00212] In some modalities, the digital asset may be or include a smart contract that is designed to be established within a predefined period of time (for example, 5 hours, 1 day, or 1 week). Alternatively, a smart contract can cause the settlement process to run alongside the next settlement lot or at a specific time of day. As explained above, the smart contract can be imposed by the computer at administrative node 550, the
Petition 870190022368, of 03/08/2019, p. 93/158
67/114 management, a central bank (which can receive a smart contract from a computer from administrative node 550) or any other suitable party. After liquidation, the digital asset can be destroyed (for example, deleted or marked as liquidated). In addition, the digital asset can be digitally signed to indicate that the settlement has been completed and the transaction record can be stored (for example, in a database list or a blockchain ledger).
[00213] In some modalities, a series of transfers of digital assets can be settled at the same time. Thus, a net position can be calculated between the sending institution's computer 560 and the receiving institution's computer 540. Instead of transferring the value of each digital asset back and forth, a net total can be transferred to any entity is net value due (for example, based on a given settlement period, including a given set of transfers of digital assets).
[00214] As mentioned above in relation to step S520, the digital asset can be supplied to the computer of recipient node 545 in a variety of alternative ways. For example, in some embodiments, instead of providing a single message directed to the computer of the receiving node 545, the computer of the sending node 565 can distribute the digital asset to several or all nodes throughout the asset transfer network (for example, example, all recipient nodes on the network). In this scenario, the computer of recipient node 545 can be one of several nodes that receive the digital asset. The computer of the recipient node 545 can recognize that the digital asset is destined for the computer of the receiving institution 540 based on a corporate ID included in the digital asset.
[00215] Alternatively, in some modalities, the computer of administrative node 550 can distribute the digital asset on behalf of the computer of issuing node 565. The computer of administrative node 550 can provide the
Petition 870190022368, of 03/08/2019, p. 94/158
68/114 digital asset directly to the computer of recipient node 545 or you can distribute the digital asset to a plurality of recipient nodes (as described above). In other embodiments, the administrative node 550 computer may instead publicly distribute updates on the transaction ledger to one or more nodes. In this scenario, the recipient node 545's computer can review the new digital assets registered in the updated ledger and identify any relevant digital assets (for example, based on corporate IDs).
[00216] In other modalities, neither the issuer 565 node computer nor the administrative node 550 computer can distribute the digital asset. Instead, the computer of administrative node 550 can continuously update a transaction ledger and the computer of recipient node 545 can have access (e.g., real-time access) to the ledger. In this scenario, the computer of recipient node 545 can regularly or continuously check a central ledger (for example, hosted by the computer of administrative node 550) for the relevant transactions.
[00217] Additionally, as mentioned above, one or more additional nodes (for example, administrative nodes, issuing nodes and / or recipient nodes) can also maintain their own accounting book and extend it based on the transfer of digital assets. However, in some embodiments, certain entities and nodes may only be able to display a subset of transactions (or significant information associated with a subset of transactions), rather than the entire ledger. For example, block bodies can be removed or obscured from some blocks when a given node accesses a central ledger or when an ledger update is sent to a given node. Thus, in some modalities, the accounting book may not be entirely public, as access may be restricted and filtered
Petition 870190022368, of 03/08/2019, p. 95/158
69/114 based on the display entity.
[00218] As mentioned with respect to FIG. 1, the sending institution's computer 560 can interact with the asset transfer network in several ways. Thus, in some modalities, steps S506S520 can occur alternatively. For example, instead of contacting the sending node 565 computer directly, the sending institution 560's computer can communicate about the digital asset with the interaction platform.
[00219] In this scenario, the sending institution's computer 560 can send the transaction request to the interaction platform. The interaction platform can then generate the digital asset (instead of the issuing node's 565 computer) or the interaction platform can request that the digital asset be generated (for example, by a node in the asset transfer network). In addition, the interaction platform (instead of the sender node 565 computer) can generate a digital signature for the digital asset based on the private key of the sender node 565 computer or the sending institution 560 computer. The interaction platform it can also perform some functions of the computer of administrative node 550, such as providing a second digital signature.
[00220] Then, the interaction platform can provide the digital asset and the digital signatures corresponding to the asset transfer network, thus publishing the transaction. For example, the interaction platform can provide the digital asset and signatures to the issuing node 565 computer and / or the administrative node 550 computer. Once the digital asset arrives at the asset transfer network, the digital asset can be distributed between nodes and delivered to the recipient node 545 computer.
[00221] The modalities of the invention provide a number of advantages. For example, the modalities provide an asset transfer network with speed, security, reliability, transparency and efficiency.
Petition 870190022368, of 03/08/2019, p. 96/158
70/114 improved. A universal and allowed network can be well organized and can enable efficient messaging in known ways that facilitate the transfer of direct value between a sender and a recipient, regardless of location. This organization can reduce extra communications, as well as remove the mystery of several unknown correspondent banking relationships, present in decentralized legacy systems.
[00222] Central registration, verification of compliance by participating entities, standardized communications and universal identifiers that uniquely identify entities can facilitate a sense of trust in the network and participating entities. This confidence can be further enhanced by knowing that network validators (for example, administrative nodes) can be limited, known, defined in advance and operated by a trusted party. A distributed ledger can instill confidence that each participating entity has the same information about contracts and transfers that were made. Likewise, digitally signed digital assets can be highly trusted, as signatures can be validated to confirm that the sending financial institution has performed proper transaction validation and that a digital asset is being legitimately transferred.
[00223] The high level of network trust and digitally signed digital assets can sufficiently reduce transaction risk to allow recipient financial institutions to make a received digital asset value immediately available in the recipient's account, even if the amount has not still been resolved. This means that a transferred amount can be available almost immediately after the transfer is initiated. Thus, regardless of how and when settlement occurs, the arrangements allow funds to be available much more
Petition 870190022368, of 03/08/2019, p. 97/158
71/114 faster than traditional transfer methods that cannot make funds available for withdrawal until settlement is completed (for example, immediately versus 3-7 days).
[00224] The use of a central settlement service entity (for example, a central bank) allows for a centralized settlement process. For example, in some embodiments, a sending bank and a receiving bank may have an account with a central bank. When the sending bank wishes to transfer an amount to a receiving bank, the amount can be transferred between their respective accounts at the central bank. Accounts can be in a single central bank location in one country, or the central bank can have multiple locations in different countries (for example, a global bank). Either way, the central bank can coordinate the transfer of value from the sending bank account to the receiving bank account. This provides a more streamlined and transparent process than the traditional correspondent banking relationships used for international wire transfers. Instead of transferring through several correspondent banks (for example, three, four, five or more transfer steps at different banks), the funds can be settled at the central bank. In addition to simplifying the settlement process, this also allows each bank to access a global asset transfer network with only one external relationship (for example, a relationship with the central bank). As a result, a particular bank may no longer need to maintain several corresponding banking relationships, which traditionally may include twenty or more relationships.
[00225] FIG. 6 shows an example of an asset transfer network 600 with additional details. FIG. 6 provides an expanded view of network asset transfer processes. For example, the center of the figure shows a detailed representation of a 650 data center, which in some ways can be similar or the same as an administrative node computer. FIG. 6 also shows how the 650 data center
Petition 870190022368, of 03/08/2019, p. 98/158
72/114 interacts with other entities, such as the sending institution's computer 660 and the receiving institution's computer 650. Each component shown in FIG. 6 can represent a computer, a software module, a process being implemented or a cloud-based service. [00226] As mentioned above, in some embodiments, data center 650 may be representative of an administrative node computer. In addition, in some embodiments, in addition to a computer representation of the administrative node, data center 650 shown in FIG. 6 may also cover other components and / or features described in relation to FIG. 1, such as interaction platform 154. For example, data center 650 may represent the management entity described above and may include some or all of the functionality provided by or associated with the management entity. Thus, data center 650 shown in FIG. 6 can alternatively be referred to as a management computer, a network computer or a transaction processing computer. In some embodiments, data center 650 shown in FIG. 6 can also represent other nodes shown in FIG. 1 in addition to only an administrative node computer 150, such as the sender node computer 165 and / or the recipient node computer 145.
[00227] FIG. 6 also shows a series of steps for the processes performed by the data center 650. The components in the asset transfer network 600 can be described in conjunction with the processes.
[00228] For example, asset transfer network 600 includes a sending institution computer 660, which can interact with data center 650 in a variety of ways. As shown by arrow 1, the sending institution's computer 660 can register with the asset transfer network. The data center 650 can first perform an authentication process 651. This may include verifying the identity of the sending institution, as well as providing access credentials (for example,
Petition 870190022368, of 03/08/2019, p. 99/158
73/114 a username and password) for the sending institution's computer 660. The sending institution's computer 660 can then perform a login process 653 in order to access the asset transfer network. After a successful login, the sending institution's 660 computer may then be able to access a 654 user interface (as shown by arrow 1.1) to interact with the 650 data center.
[00229] In some modalities, before being able to send digital assets, the computer of the sending institution 660 can first complete the 650F integration process. As shown by arrow 1.2, the sending institution's computer 660 can provide all necessary information to data center 650. As shown by arrow 1.3, integration can include risk analysis, compliance verification, data collection from the user (for example, information about the sending institution's computer 660 and / or customers of the sending institution) and providing the information to the computer of the sending institution 660 about digital asset networking procedures. The 650F integration process can be performed by and / or similar to the 150F enrollment module shown in FIG. 2. In addition, the risk analysis component can be performed by the risk management computer 157 shown in FIG. 1 and / or the risk module 150H shown in FIG. 2.
[00230] As shown by arrows 1.4 and 1.5, once responses are received and integration is complete, data center 650 can store information about the sending institution's computer 660 in database 656. Thus, in some embodiments, database 656 may be similar to the database of user 150Q shown in FIG. 2.
[00231] As shown by arrow 1.6, the data center 650 can cause an account to be established for the sending institution's computer 660 through a 650X creation module (for example, for the creation of new accounts and / or digital assets). For example, the 650X design module can create an account identifier (for example, an ID
Petition 870190022368, of 03/08/2019, p. 100/158
74/114 corporate) to be established that can represent the sending institution's computer 660 during transfers of digital assets. As shown by arrow 1,7, this account information can also be stored in the 656 database.
[00232] In some modalities, after successful registration and integration, the sending institution's computer 660 can initiate a transfer of digital assets. As shown by arrows 2 and 2.1, the sending institution's computer 660 can log in and access the data center 650 user interface. As shown by arrow 2.2, the sending institution 660's computer can request a transfer of digital assets, providing information about the transfer of digital assets (for example, recipient, quantity, etc.) to a 650P transaction processing module.
[00233] The 650P transaction processing module can validate the transaction request (for example, similar to the 150J validation module in FIG. 2), as well as determine any fees and / or exchange rates to be applied to the transfer of assets digital. Then, in step 2.3, data center 650 can inform the receiving institution 660's computer to credit a recipient account (for example, a resource provider account) with the final amount (for example, the value of the digital asset minus any fees after currency exchange). Also, as shown by the arrow
2.4, the transaction details can be stored in database 656. Consequently, database 656 can be similar to the transaction repository 156 shown in FIG. 1.
[00234] When the details of the transaction are ready, the information can be passed to a 650M digital asset preparation module, as shown by arrow 2.5. The 650M digital asset preparation module can then generate a digital asset based on the details of the transaction, as well as temporarily store the digital asset in the bank
Petition 870190022368, of 03/08/2019, p. 101/158
75/114 of data 656, as shown by arrow 2.6. Thus, the 650M digital asset preparation module can be similar to the 150M digital asset module shown in FIG. 2. The 650M digital asset preparation module can also prepare to store the digital asset in a blockchain ledger, providing the digital asset to a 65 OQ recording module from a 65 OV blockchain application interface, as shown by arrow 2.7. The 2.8 arrow can be an acknowledgment of receipt and / or a request for digital signatures.
[00235] As shown by arrow 2.10, the 650M digital asset preparation module can request a 650P hardware security module for one or more digital signatures. For example, the 650P hardware security module can generate a digital signature using a private key associated with the 650 data center. In some embodiments, the 650P hardware security module can also generate a digital signature using a private key associated with the computer. sending institution 660. Thus, the hardware security module may be similar to the key database 150P and / or the signature module 150K in FIG.
2. Digital signatures can go back to the 650M digital asset preparation module, as shown by arrow 2.11.
[00236] As shown by arrow 2.12, digital signatures and / or the filled digital asset can be supplied to the 650Q recording module. At that point, the 650V blockchain application interface can route digital assets and digital signatures to a 650D blockchain application. The 650D blockchain app can update a blockchain ledger with the new digital asset (for example, which may include creating a new block), as well as creating a smart contract based on the digital asset. For example, as shown in FIG. 6, the 650D blockchain app can create a digital record that shows that a value is promised from a sending institution account (or a specific user account within
Petition 870190022368, of 03/08/2019, p. 102/158
76/114 from a set of user accounts associated with the sending institution) to a receiving institution account (or a specific user account within a set of user accounts associated with the receiving institution). Consequently, the 65OD blockchain app can be similar to the 150L ledger update module and / or 150D ledger database).
[00237] In some embodiments, as shown in FIG. 6, a transfer of value from a sending institution to the receiving institution can be performed using a data center (or other central entity) as a mediator. For example, the amount can be transferred from a sending institution account to a data center account, and then the amount can be transferred from the data center account to a receiving institution account.
[00238] Once the digital asset is registered in the blockchain ledger, data center 650 can store a copy of the digital asset and / or block in the 656 database (for example, similar to the transaction repository 156 shown in FIG. 1.), as shown by arrow 2.13. In addition, data center 650 can send a message to the computer of the receiving institution 640 (or a computer of the recipient node), informing that the digital asset has been processed and the value of the transaction is guaranteed. In some embodiments, the computer of the receiving institution 640 (or a computer of the recipient node) can also access a copy of the blockchain ledger to detect the newly recorded digital asset (for example, displaying a limited read-only display version of the blockchain accounting book stored by blockchain application 650D).
[00239] As shown by arrow 4, in some embodiments, the sending institution 660's computer may contact data center 650 in a different way. For example, the sending institution's computer
Petition 870190022368, of 03/08/2019, p. 103/158
77/114
660 can operate a sending node and thus can generate the digital asset and / or generate a digital signature (for example, using a separate hardware security module). The sending institution's computer 660 or the issuing node's computer can then send the prepared digital asset and digital signature to the data center 650, as shown in arrow 4. An interface (for example, the 658 adapter) can receive the digital asset and forward it to the 650P transaction processing module. The digital asset transfer process can then proceed as described above, except the 650 data center can skip the steps of generating the digital asset and digital signature associated with the sending institution. In addition, the data center 650 can verify the authenticity of the received digital signature (for example, similar to the 150G verification module in FIG. 2) [00240] Subsequently, after posting a digital asset to the accounting book and informing the stakeholders, the data center 650 can coordinate the settlement of the digital asset value. For example, after a defined period of time, or when a smart contract is triggered in another way, settlement service 655 can cause the amount to be settled between a sending institution account and a receiving institution account. Consequently, settlement service 655 may be similar to the settlement service computer 155 shown in FIG. 1. In some modalities, the settlement service 655 can obtain information about new digital assets from the 650M digital asset preparation module, as shown by arrows 3.1 and 3.2. Settlement service 655 can update database 656 to indicate that settlement is initiated, as shown by arrow 3.3. Settlement service 655 can cause the amount to be transferred and information to the receiving institution's computer 640 that the amount has been settled (for example, at a central bank), as shown by arrow 3,4. Finally, settlement service 655 can update database 656 to indicate
Petition 870190022368, of 03/08/2019, p. 104/158
78/114 that the value of the digital asset has been successfully resolved, as shown by arrow 3.5.
Network Topology [00241] FIG. 7 shows a diagram of an example network topology that can be used with embodiments of the invention. The modalities of the invention allow network processes such as registration, creation of digital assets, updating the ledger and storage of the ledger to be distributed. FIG. 7 provides an example configuration to achieve this network distribution and redundancy.
[00242] FIG. 7 includes a routing computer 770, a first data center 750, a second data center 850, and a key management computer 780. The routing computer 770 may initially receive requests for transferring digital assets (for example, from a sending institution or a computer from the sending node) through a 775 firewall. The 770 routing computer can then determine which data center to process the digital asset and can forward the request for transferring digital assets to the data center determined.
[00243] In some embodiments, a data center can be the same or similar to an administrative node computer (for example, as described in FIGS. 1, 2 and 6) and each data center can alternatively be referred to as a computer the administrative node. For example, similar to an administrative node computer, a data center can manage an asset transfer network by processing transactions (for example, validating and signing digital assets) and maintaining a transaction accounting book (for example, a blockchain). In addition, as explained above in relation to the data center shown in FIG. 6, a data center may instead represent the management entity described above and may also include some or all of the functionality provided by the management entity. For example, a data center can also
Petition 870190022368, of 03/08/2019, p. 105/158
79/114 cover other components and / or features described in relation to FIG. 1, as the interaction platform 154. Thus, a data center can alternatively be referred to as a management center, a network center or a transaction processing center (each of which may include one or more server computers). In some embodiments, a data center can also represent other nodes shown in FIG. 1, such as the computer of the sending node 165 and / or the computer of the receiving node 145.
[00244] As shown in FIG. 1 and FIG. 4, an asset transfer network can include multiple computers from the administrative node. Likewise, FIG. 7 includes multiple data centers. Incorporating multiple data centers into an asset transfer network offers several advantages. For example, the processing load of received digital assets can be divided between data centers, so that digital assets can be processed quickly. Multiple data center locations provide several possible destinations for incoming digital asset requests, and the 770 routing computer can intelligently route each incoming digital asset to the most appropriate data center. For example, the 770 routing computer can send a digital asset request to the data center with the shortest backlog (for example, to evenly distribute processing loads), to the data center closest to the requester (for example , in the event that data centers are geographically distributed) or to a specific data center based on any other appropriate consideration. As a result, inbound digital assets can be validated, signed, posted to a blockchain ledger and otherwise processed more efficiently.
[00245] In addition, each data center can store and maintain a separate copy of the blockchain ledger. As a result, the security of the blockchain ledger is increased through redundancy.
Petition 870190022368, of 03/08/2019, p. 106/158
80/114 [00246] Although digital assets are initially processed by a single data center, data centers can share information about newly approved digital assets (for example, or newly created blocks) with each other. For example, the first data center 750 can provide updated messages to the second data center 850 about new digital assets and / or new blockchain blocks. The first 750 data center can also receive similar update messages from the second 850 data center about new digital assets or blocks created or completed in the second 850 data center. As a result, both data centers can store complete copies of the transaction ledger, even if each processes only a portion of the digital assets.
[00247] In addition, when the second 850 data center receives an accounting book update from the first 750 data center, the second 850 data center may validate each new digital asset and / or block before updating its own accounting book. Thus, each digital asset and / or block can be validated and approved by each data center, thus providing additional opportunities to detect digital assets and inappropriate behavior. Thus, there are additional lines of defense after a digital asset is initially validated and registered on a blockchain block in the first 750 data center.
[00248] In combination, the various data centers can create a complete accounting book that is centrally managed by the network operator. However, separating individual data centers and placing them in different locations allows transaction processing and block creation to be distributed. As a result, the transaction processing throughput is increased, as long as the unchanging ledger is maintained. The data in the blockchain ledger is distributed for redundancy, but still the control of a single central network operator (and therefore not vulnerable to malicious changes).
Petition 870190022368, of 03/08/2019, p. 107/158
81/114 [00249] FIG. 7 describes a network with distributed data centers that can create blockchain blocks independently and then update another one to synchronize their respective blockchain records. For exemplary purposes, FIG. 7 is described in the context of the transfer of digital assets. However, the modalities apply equally to any other suitable communication and / or record-keeping network that may use distributed data centers. For example, distributed data centers can be applied to asset transfer networks that facilitate the transfer of any suitable type of digital asset (or other value), such as access credentials, event tickets, property rights, currency, credit games, mobile phone minutes, digital media, currency, etc.
[00250] Even more generally, distributed data centers can be used to record any type of suitable data element. For example, data elements that represent up-to-date medical information, information about a newly issued university degree, test results, vehicle registration data, signed exemptions and / or any other suitable type of recordable information can be tracked and recorded. Any suitable type of digital record can be used to track new data elements. For example, instead of a blockchain ledger, data elements can be stored in a simple list format.
[00251] While FIG. 7 shows two data centers (that is, the first data center 750 and the second data center 850), any suitable number of data centers can be included in an asset transfer network. Including additional data centers can further improve network efficiency and redundancy in the ledger.
[00252] As shown in FIG. 7, the first 750 data center can include a number of components. These components can be similar
Petition 870190022368, of 03/08/2019, p. 108/158
82/114 to the computer components of the administrative node shown in FIG. 2 and / or similar to the data center components shown in FIG. 6. Instead of illustrating all the components in FIG. 2 and FIG. 6, FIG. 7 is provided to demonstrate how multiple distributed data centers can operate within an asset transfer network. The first data center components 750 shown in FIG. 7 include a 750A processing computer including one or more processing applications, a 750E rules computer, a 750K signature computer, a 750D ledger database, a 750P key database, one or more databases additional data (for example, 750C database computer and 750Q database computer), a 750N encryption computer, and any other suitable hardware or software modules. The modalities allow each of these components to take the form of separate server computers. Alternatively, in some modalities, one or more of these components may take the form of software modules running on one or more server computers. In any case, as a whole, the first data center 750 can be referred to as a first data center computer. Likewise, the second 850 data center can be referred to as a second data center computer.
[00253] The 750A processing computer may include hardware processors and / or software modules for receiving and processing requests for transferring digital assets. For example, the 750A processing computer can receive and validate a digital asset, obtain a digital signature for a digital asset, add a digital asset to an accounting book (for example, create a new blockchain block that includes the digital asset) and perform any other appropriate task to process digital assets. The 750A processing computer can also facilitate network registration of other entities. In
Petition 870190022368, of 03/08/2019, p. 109/158
83/114 In some embodiments, the 750A processing computer can perform all of the activities described above with respect to an administrative node computer. For example, the 750A processing computer can perform activities associated with some or all of the modules included in the computer-readable medium of FIG. 2.
[00254] The 750A processing computer may include one or more processing application modules, which are represented in FIG. 7 App 1, App 2, App 3 and App n. These application modules can represent different hardware processors or virtual machines to receive and process transfer requests for different digital assets. The different processing application modules can be used to process multiple input digital assets at the same time. Processing application modules can divide processing tasks to promote load balancing.
[00255] In some embodiments, the 750A processing computer may include instructions for, after creating a new block or adding a new digital asset to the transaction accounting book, sending information about the record update (for example, a new block ) for the second 850 data center. Consequently, the processing computer 750A can perform the functions described in relation to the 150L ledger update module in FIG. 2. These ledger updates can be distributed after each digital asset has been minted, after each block is created, every second, every 10 seconds, every minute or any other suitable time interval. The modalities allow a new block to include information about a single digital asset, ten digital assets, each digital asset created within a certain period of time and / or any other appropriate number of digital assets.
[00256] Additionally, in some modalities, the
Petition 870190022368, of 03/08/2019, p. 110/158
84/114 750A processing can include instructions for receiving information about newly completed digital assets and / or blocks from the second 850 data center, as well as validating those digital assets and / or blocks. For example, the 750A processing computer can validate the authenticity of each digital asset in a block, validating the accompanying digital signatures. The 750A processing computer can also validate each blockchain block by validating the block header. For example, the processing computer 750A can confirm that the block header is the output of a hashing algorithm when some or all of the data in the block body is inserted into the hashing algorithm. The 750A processing computer can also confirm that each block relates correctly to the previous block. For example, the 750A processing computer can make sure that a link to the previous block, such as the previous block header, is included in the block body.
[00257] The 750E rules computer can include instructions for processing digital assets and can include logic and rules specifically associated with the first 750 data center. In some embodiments, the 750E rules computer can store the instructions used by the 750A processing computer. For example, the rules computer 750E can store instructions similar to or the same as one or more of the modules included in the computer-readable medium of FIG. 2. In some embodiments, the rules computer 750E may also include instructions for settlement transactions or may interact with a settlement service (for example, settlement settlement computer 155 in FIG. D [00258] 750D ledger can store information about processed and issued digital assets. For example, a blockchain transaction ledger can be stored in the 750D ledger database.
Petition 870190022368, of 03/08/2019, p. 111/158
85/114 embodiments, the 750D ledger database may be similar to or the same as the 150D ledger database in FIG. 2.
[00259] The 750P key database can include one or more encryption keys associated with one or more entities. For example, the 750P key database can include a private key from the first 750 data center for creating digital signatures. The 750P key database can also include one or more public keys associated with other entities (for example, issuing nodes and recipient nodes) to validate digital signatures and digital assets. In some embodiments, the 750P key database can take the form of a hardware security module (HSM). In some embodiments, the key database 750P may be the same as or similar to the key database 150P in FIG. 2.
[00260] The 750K signature computer can be configured to create digital signatures using private keys and / or validate digital signatures using public keys. The 750K signature computer can be used to digitally sign a digital asset, a blockchain block, an entire blockchain ledger and / or any other information that needs to be verified. In some embodiments, the 750K signature computer can access the encryption keys stored in the 750P key database. In some embodiments, the 750K signature computer may be the same as or similar to the 150K signature module in FIG. 2.
[00261] The 750N encryption computer can run any suitable encryption service. For example, ledger updates sent to the second 850 data center can be encrypted, and likewise, ledger updates received from the second 850 data center can be decrypted.
Petition 870190022368, of 03/08/2019, p. 112/158
86/114 [00262] The 750C and 750Q database computers can be used to store any suitable information. For example, the 750C database computer can store a transaction backup ledger (for example, similar to database 656 in FIG. 6), while the 750Q database computer can store user data ( for example, similar to user database 156Q in FIG. 2) and / or node information (for example, similar to node database 156C in FIG. 2). In some embodiments, one or more database computers can be used to store application metadata, logic and rules for processing transactions, temporary transaction data while a digital asset is being processed and / or a set of digital assets for the which a block is being created.
[00263] In some embodiments, the first data center 750 and the second data center 850 may include similar components and / or functionality. Thus, in some embodiments, any description of the first data center 750 can equally apply to the second data center 850 and any description of the second data center 850 can equally apply to the first data center 750.
[00264] The key management computer 780 can control the distribution and exposure of encryption keys. For example, when a sending institution (or any other suitable entity) registers with the asset transfer network, a key pair associated with the sending institution can be established. The 780 key management computer can distribute information about the new key pair to one or more data centers. For example, the issuing institution can register on the network through the first data center 750. The key management computer 780 can obtain the key pair from the first data center 750 and provide it (along with other registration details) for the second data center
Petition 870190022368, of 03/08/2019, p. 113/158
87/114
850. As a result, both the first 750 data center and the second 850 data center may be able to validate digital signatures created by the sending institution and otherwise process requests for transferring digital assets received from the sending institution.
[00265] An 800 method for processing transactions and combining digital records in an asset transfer network with multiple data centers can be described in relation to FIG. 8, according to the modalities of the invention. The method describes the storage of digital assets in a blockchain ledger. However, modalities can also be used to record other types of data elements.
[00266] As explained above, a computer of the sending institution, a computer of the issuing node or any other suitable entity can send a transfer request for digital assets to send a digital asset to a recipient. In some embodiments, a computer from the issuing node can create a digital asset, digitally sign the digital asset and include the digital asset and signature in the order in order to obtain validation and approval of a network administrator's digital asset (for example , as described in relation to step S508 in FIG. 5).
[00267] In step S805, which can be similar to step S510 in FIG. 5, the routing computer 770 can receive the transfer request for digital assets through a 775 firewall. For example, in some embodiments, all transfer requests for digital assets can be sent directly to the routing computer 770. In in other ways, requests for transferring digital assets can instead be sent to a data center (for example, the nearest data center) and each data center can include a routing module.
[00268] In step S810, routing computer 770 can determine a data center to process the transfer request for
Petition 870190022368, of 03/08/2019, p. 114/158
88/114 digital assets. The determination can be based on a number of factors. For example, the 770 routing computer can send the transfer request for digital assets to the nearest data center (for example, for faster transmission and processing). The 770 routing computer can instead prioritize load balancing and send the transfer request for digital assets to the data center with the most available processing power or the most available processing application modules.
[00269] In some embodiments, the routing computer 770 can also assign a priority level to an incoming digital asset transfer request. For example, requests for transferring digital assets associated with a particular entity (for example, a particular sending institution, issuing node, user, recipient, etc.) may be given higher priority for faster processing.
[00270] In addition, in some modalities, the 770 routing computer can determine whether a request for transferring digital assets should be processed or rejected. For example, a request that is incorrectly formatted or associated with an unknown requestor can be rejected immediately.
[00271] In step S815, the routing computer can transmit the transfer request for digital assets to the given data center. For example, the transfer request for digital assets can be sent to the first data center 750. In some embodiments, the routing computer 770 can transmit the transfer request for digital assets only to the first data center 750, and not to any other data centers. The first 750 data center can process the request and can later provide information about the processed digital asset to other data centers.
Petition 870190022368, of 03/08/2019, p. 115/158
89/114 [00272] In step S820, the first 750 data center can validate the digital asset, the digital signature and / or any other appropriate information. For example, the first 750 data center can also confirm that the sending entities (for example, the sending node's computer and the sending institution's computer) are properly registered and in compliance with the processing rules. In some embodiments, step S820 may be similar to step S512 in FIG. 5.
[00273] In some modalities, the request for transfer of digital assets may not include a digital asset. In this case, step S820 may include the generation of the digital asset and / or the generation of an additional digital signature associated with a sending entity.
[00274] In step S825, the first data center 750 can generate a second digital signature for the digital asset (for example, using a private key associated with the first data center 750). The first 750 data center can also create a smart contract and / or perform any other appropriate transaction processing tasks. In some embodiments, step S830 may be similar to step S514 in FIG. 5.
[00275] Thus, the first data center computer can process a first digital asset that indicates the transfer of a value from a sender to a recipient by performing steps S820-S825, as well as any other appropriate steps.
[00276] In step S830, the first data center 750 can add the digital asset to a transaction ledger, which can be stored locally in the first data center 750 (for example, in the 750D ledger database). For example, the first 750 data center can create a new blockchain block with a block body and a block header. The block body can include registration information (for example, information about the digital asset) and, optionally, additional digital assets that are being processed over a period of time
Petition 870190022368, of 03/08/2019, p. 116/158
90/114 similar. The block body can also include a reference to a previous block, such as a previous block header. In some embodiments, some or all of the block body information can be used to generate the block header. For example, the block body can be entered into a hash algorithm, a cryptographic algorithm and / or any other suitable data manipulation process and some or all of the output can be used as the block header. In some embodiments, step S830 may include accounting book construction processes similar to those described in relation to step S516 in FIG. 5.
[00277] For purposes of description, this step can be considered by creating a first block for a first blockchain. However, the term first does not necessarily mean that this is the beginning of the blockchain. Instead, the first blockchain can be an existing blockchain with a number of existing blocks and the first block can be added to the end of the existing blockchain.
[00278] In step S835, the first data center 750 can send a response to the requester of the transfer of digital assets (for example, a computer from the sending node or a computer from the sending institution). For example, the first 750 data center can send a binary response indicating whether the digital asset has been successfully processed (for example, and added to the transaction ledger) or rejected. In some embodiments, step S830 may be similar to step S516 in FIG. 5.
[00279] In addition, the first 750 data center can send a message to a recipient (for example, a computer at the recipient node or a computer at the receiving institution) stating that a digital asset has been processed that indicates that a value will be provided to the recipient . In some embodiments, that aspect of step S830 may be similar to step S520 in FIG. 5. However, the first 750 data center can send a message instead of a computer from the sending node. Like this,
Petition 870190022368, of 03/08/2019, p. 117/158
91/114 both the sender and the receiving party can be informed that the digital asset is posted in a blockchain ledger and, optionally, a smart contract has been established.
[00280] At this point, the digital asset can be fully processed and the ledger updated locally on the first data center 750. However, to maintain a uniform transaction ledger on the network, the first 750 data center can proceed to update one or more data centers with information about the digital asset and / or other accounting book updates.
[00281] In step S840, the first data center 750 can transmit a message with information about recent ledger updates to the second data center 850. For example, the message can include information that identifies the first data center 750 (for example , distinguish it from other data centers), information about a new digital asset, information about a new block (for example, a block header and / or block body data), a time stamp, a return and / or any other appropriate information. The message may also include a request for information about recent updates to the blockchain ledger in the second 850 data center. In some embodiments, the first 750 data center can encrypt some or all of the ledger update information for submission (by example, using a symmetric key or a public key from the second 850 data center). Thus, the first data center computer can send a message to a second data center computer indicating that the first block was created for the first blockchain, where the message includes the block header, block body and / or any other adequate information.
[00282] In step S845, the second data center 850 can receive the update information from the accounting book of the first data center
Petition 870190022368, of 03/08/2019, p. 118/158
92/114
750 and then validate the transaction information or perform any other appropriate processing. For example, the second 850 data center can validate each digital signature associated with the new digital asset (for example, using relevant public keys). The second 850 data center can also confirm that a block header is a correct hash of the digital asset information, the previous block header and / or other suitable block body information. The second data center 850 can also verify that the previous block indicated in the current block body is the correct and expected previous block. In some embodiments, the second data center 850 may first decrypt the update message from the first data center 750 (for example, using a symmetric key or corresponding private key).
[00283] While the second 850 data center can validate the digital asset and / or block, in some modalities, the second 850 data center cannot repeat all transaction processing performed by the first 750 data center. For example, the second data center 850 cannot verify that each entity associated with the digital asset is registered in the asset network and in accordance with the network rules. In addition, the second 850 data center cannot create another digital signature for the digital asset and / or block. However, in other embodiments, the second 850 data center can fully repeat transaction processing and perform some or all of these steps.
[00284] In step S850, the second 850 data center can add the digital asset and / or block in its own locally stored transaction ledger or otherwise update the ledger with the ledger update information accounting received from the first data center 750. For example, the second data center 850 can copy the received block to form the first data center 750 and add it to its own blockchain accounting book. This can be considered by creating a second block (for example, because it is for a different blockchain), but the
Petition 870190022368, of 03/08/2019, p. 119/158
93/114 second block is the same as the first block. As explained below, the second 850 data center can block the entire block (for example, both the header and the body) to the blockchain or the second 850 data center can only use the block header.
[00285] In some embodiments, the second 850 data center may create a new transaction block including one or more digital assets received from the first 750 data center. The new block may include additional digital assets that are being processed in the second 850 data center or it can only include digital assets received from the first data center 750. In some embodiments, the second data center 850 can also generate an additional digital signature (for example, using a private key from the second data center 850) to indicate that the information received from the first data center data center 750 has been validated and approved by the second data center 850. Thus, the second data center computer can add the first block header, block body and / or digital asset records to a second blockchain [00286] In some embodiments, if the second 850 data center is unable to validate the digital asset, block header, or block body received from the first data center 750, the second 850 data center may reject the ledger update information and not add it to the second 850 data center ledger. In that case, the second 850 data center may also inform the first 750 data center that the ledger update accounting has been rejected and the first 750 data center can then audit its own transaction accounting book, possibly identifying and removing (or flagging) inappropriate transaction records.
[00287] As explained above, the second 850 data center can also receive and process requests for transferring digital assets, create new blocks and provide accounting book updates for the first
Petition 870190022368, of 03/08/2019, p. 120/158
94/114 data center 750. In other words, a second data center computer can process a second digital asset and then register the second digital asset by creating another block on the second blockchain. This new block can be referred to as a third block, as it is created after the first block (on the first blockchain) and the second block (the copy of the first block on the second blockchain). The second data center can then send a second message to the first data center computer indicating that the second digital asset has been registered in a third block on the second blockchain. When the first data center computer receives the second message from the second data center computer, the first data center computer can update the first blockchain ledger by adding a fourth block, which can be a copy of the third block (e.g. the header and / or body).
[00288] As a result, both the first 750 data center and the second 850 data center can update their local transaction accounting books to match, even if a digital asset is initially received and processed in only one of the data centers. Each data center can include a transaction accounting book with the same list of digital assets. For example, each data center can have a similar blockchain with the same list of blocks (for example, headers and / or bodies). Thus, each data center can have a complete list of all digital assets and / or blocks created across the entire network of digital assets.
[00289] In some modalities, each data center may have an identical blockchain ledger with a corresponding set of digital asset records. In other modalities, each data center can have a blockchain accounting book that includes all digital assets, but the different blockchain accounting books can have digital assets and / or blocks listed in a different sequence. As a result, block headers can also have different values (for example, if the
Petition 870190022368, of 03/08/2019, p. 121/158
95/114 headers are generated based on the digital assets recorded in the block). [00290] In some modalities, data centers can achieve exact correspondence of blockchain accounting books (for example, blocks with the same headers, even ordering of digital assets, etc.) alternating when sending each other accounting book update. For example, the first data center 750 can send an accounting book update (for example, with a first block) to the second data center 850, then the second data center 850 can send an accounting book update (for example example, with a second block) to the first data center 750, then the first data center 750 can send another update (for example, with a third block) to the second data center 850, and so on. Updates can alternate in this way in a regular, periodic pattern (for example, an update is sent every 10 seconds, 30 seconds, 1 minute, 10 minutes, etc.) and the blocks can reference each other in the appropriate sequence.
[00291] In other words, the second data center 850 can add the first exact block received from the first data center 750 to its own ledger. Then, the second 850 data center can create a second block based on digital assets that it processed locally (for example, at the last minute) and add the second block to your ledger. The second block can reference the first block (for example, generating the second block header based in part on the first block header), so that the second block is subsequent to the first block on the blockchain. The second data center 850 can then send the second block to the first data center 750. Once the first data center 750 receives the second block and adds it to its blockchain ledger, the cycle can repeat itself. For example, the first 750 data center can wait to create a third block (for example, with
Petition 870190022368, of 03/08/2019, p. 122/158
96/114 basis on newly processed digital assets) until after receiving the second block and adding it to your ledger. After the second block is added, the third block can be created so that it references the second block. The first data center 750 can then send the third block to the second data center 850 and the process can continue to cycle this way. As a result, the first data center 750 and second data center 850 can have blockchain accounting books with the same blocks ordered in the same sequence.
[00292] As explained above, there may be additional data centers, such as a third data center. In this case, the first 750 data center can distribute ledger updates to each additional data center directly or indirectly. For example, the first 750 data center can send accounting update messages directly to each data center. Alternatively, the first data center 750 can send an accounting book update message directly to the second data center 850, which can forward the accounting book update message to the third data center (and so on). The accounting update message sent to the second 850 data center can include an instruction to forward the update to the third data center.
[00293] In other modalities, different data centers may have slightly different configurations. For example, different data centers may have different rules and procedures for processing digital assets, creating block chains and / or sharing accounting information. Data center rules can be adjusted based on data center processing power, location, affiliation or any other suitable reason. For example, network end users, a specific financial institution, or any other suitable entity may wish to restrict accounting information for privacy or,
Petition 870190022368, of 03/08/2019, p. 123/158
97/114 otherwise, want increased data center operations.
[00294] For illustrative purposes, FIG. 9 shows a diagram of an asset transfer network with different groups of data centers. FIG. 9 includes three groups (A, B and C) and each group includes two data centers.
[00295] In some modalities, groups can be separated based on the processing power and storage capacity of the database. For example, group A may include data centers configured for processing high-volume digital assets and, therefore, may receive greater amounts of transfer requests for digital assets (for example, from a routing computer). In addition, group A may include data centers that can store, reference and otherwise manage the most detailed blockchain accounting books. In contrast, group B may include data centers that can process fewer requests for digital assets and that can only manage more limited blockchain ledgers. As a result, group B may not include comprehensive transaction data for each digital asset in the blockchain ledger or may not include all block bodies.
[00296] In other modalities, groups can be separated based on geographic location. For example, group A can include data centers located in China, group B can include data centers located in the United States, and group C can include data centers located in the United Kingdom. Alternatively, groups can be separated based on institutions with which they are affiliated. For example, group A can include data centers associated with a first financial institution, group B can include data centers associated with a second financial institution and group C can include data centers associated with a third financial institution. Any other type of suitable grouping can occur, such as groupings based on government versus private affiliation, groupings based on the type of transaction (e.g., person-to-business,
Petition 870190022368, of 03/08/2019, p. 124/158
98/114 person-to-person and company-to-company), etc.
[00297] Different groups of data centers may include different rules and procedures for processing transactions. For example, data centers in group A can be configured to process a specific volume or type of digital assets or digital assets associated with a given region. Thus, the 770 routing computer can determine to send certain requests for transferring digital assets to data centers in group A if the incoming request is associated with entities in a particular region or if the incoming request has any other specific quality for which group A was designed for.
[00298] In addition, two data centers within the same group may interact differently with each other than with a third data center in a different group. For example, group B cannot be configured to receive and store group A ledger updates with comprehensive transaction details or complete block information (for example, due to processing or storage limitations). In addition, group A may be associated with an entity (for example, an organization, a service provider, or a region) that does not want transaction data to be shared outside the group. Thus, the first data centers 750 and the second data center 850 in group A can be configured to share transaction data with each other, but not with other data centers in other groups. For example, information in the body of a block or digital asset cannot be shared outside the group, such as the date and time of the transfer, the transfer amount, and the identification information of the transfer participants (for example, the sender and the receiver of the transfer amount).
[00299] In some modalities, as long as transaction data and block bodies cannot be shared, block headers can still be shared with data centers outside group A, once
Petition 870190022368, of 03/08/2019, p. 125/158
99/114 that a block header may not convey significant transaction information. For example, a block header can be a hashed version of transaction data (for example, the block body), where transaction data cannot be derived from a one-way hash. In some embodiments, subsequent blocks or block headers can be generated based in part on the previous block header. Thus, share block headers allow all data centers, regardless of group membership, to continue building a synchronized blockchain.
[00300] Thus, in some modalities, data centers in group A may send ledger updates from other data centers in other groups, but the transaction data or block body can be removed (or obscured) in a similar way , as described above, in relation to light knots and filtered accounting books. However, here the transaction data or block body is removed when a data center (for example, an administrative node) in the first group is viewing the ledger data created in a second group data center, as opposed to when the non-administrative entity, such as a sender or recipient node, is viewing an accounting book. In other words, a single central entity that maintains the ledger can restrict itself from displaying some transaction data and blocking body information. This is possible because the single central entity can be implemented as a distributed set of data centers with different capacities, purposes and / or affiliations.
[00301] A method 1000 for distributing ledger updates limited to data centers with different rules or a different association can be described in relation to FIG. 10, according to the modalities of the invention. The method describes the storage of digital assets in a blockchain ledger and the sharing of
Petition 870190022368, of 03/08/2019, p. 126/158
100/114 some information between blockchain accounting books. However, modalities can also be used to record other types of data elements and share some information between records. [00302] In method 1000, data centers in group A can share transaction data (for example, blocking body data) with each other, but not with data centers in other groups, as described above. Thus, as described above for steps S805-S850 in method 800, the first data center 750 can receive and process requests for transferring digital assets, create a new block for a blockchain and share information about processed digital assets and the new block with the second 850 data center (which is in group A). The first data center 750 can then prepare to send an accounting update to a third data center 950 in group B, but it can first adjust the accounting update message (for example, by removing the transaction data from the message).
[00303] In step S855, the first data center 750 can remove the transaction data from the ledger update message. For example, the first 750 data center can remove digital asset information from the accounting update message, such as information that identifies the sender or recipient, a transfer amount, a time and date, and / or any other appropriate information. This may include removing some or all of the data from the message block body. However, the first data center 750 does not remove the block header (or other suitable transaction identifier or transaction group identifier).
[00304] In step S860, the first data center 750 can send the accounting update message with the transaction data removed to the third data center 950. For example, the first data center 750 can send the block header, but not the block body, for the third date
Petition 870190022368, of 03/08/2019, p. 127/158
101/114 center 950. As a result, the third data center 950 can receive a block header (or other suitable ledger entry identifier) without a block body (or other significant digital asset information) leaving group A Even in the case where the block header was calculated based on the block body (for example, using a unidirectional hash and / or encryption), the third data center 950 may not be able to derive the block body from the block header. block (for example, due to a one-way hash, or because the third data center 950 does not have access to the keys required for decryption).
[00305] In step S865, the third data center 950 can validate the block header and / or other accounting book update information received from the first data center 750. For example, the third data center 950 can confirm that the header has an appropriate length or pattern or verify using a zero proof of knowledge.
[00306] In some embodiments, the third data center 950 can receive a digital signature created by the first data center 750 for an asset or digital block and the third data center 950 can validate the digital signature using a public key associated with the first data center 750 However, the third data center 950 cannot perform some of the same types of validation or as many validation steps as the second data center 850 performs in step S845 in FIG. 8, since the third data center 950 may not have access to the block body.
[00307] In step S870, the third data center 950 can add the block header to its locally stored ledger. For example, the third data center 950 can create a new block for the local blockchain. The new block can include the received block header, but not the block body (for example, because it was not supplied). In some embodiments, the new block may only have one header (for example, which may be the same as the received header) and the new block may not have
Petition 870190022368, of 03/08/2019, p. 128/158
102/114 any information in your block body.
[00308] The block header can be used as a link to connect future blocks to the blockchain. For example, when the third data center 950 generates a subsequent block for digital assets processed locally, the subsequent block header can be generated based in part on the block header received from the first data center 750.
[00309] For example, in step S875, the third data center 950 can complete the processing of one or more local digital assets and add to the local transaction ledger. This may include generating an additional block for the local blockchain based on the digital assets processed locally. In some embodiments, the block body may include information about digital assets processed locally, the previous block header (which is the header received from the first 750 data center), a time stamp, information identifying the third 950 data center as the creator of the block and / or any other appropriate information. Then, the modalities allow the block header for the block to be hashed, encrypting or otherwise manipulating some or all of the information in the block body. As a result, the block header received from the first data center 750 is referenced by a subsequent block and thus incorporated into the block character and block headers in the third data center 950 blockchain.
[00310] Thus, the blockchain in the third data center 950 can continue to build using correct references to previous blocks and the blockchain can be complete in which some link information (for example, a header) is included about each block created in the network, even if the block body data is removed. While blockchain ledgers stored in different data centers may not match exactly due to missing digital asset information
Petition 870190022368, of 03/08/2019, p. 129/158
103/114 (for example, missing block bodies), can at least have corresponding block headers.
[00311] The third data center 950 may, at a later time, wish to refer to the blockchain of the first data center. For example, the third data center 950 may seek to obtain transaction data or the block body that has been removed or to confirm that a specific digital asset has been issued (for example, in response to a transaction dispute).
[00312] In step S880, the third data center 950 can send a request for transaction data or the entire block body to the first data center 750. The third data center 950 can indicate that it wants to receive transaction data for transactions that have occurred on a given day (or other appropriate period of time) or transaction data that matches some specific information (for example, a transaction between a specific sender and a recipient, or including a particular corporate ID).
[00313] In step S885, the first data center 750 can determine whether to provide transaction data (or the entire block body) to the third data center 950. For example, the first data center 750 can analyze the rules regarding amount of information that can be disclosed upon request (for example, restrictions based on the type of data center requesting, restrictions related to the age of the transaction, etc.). The first data center 750 can also determine whether or not it has the desired transaction data (for example, a transaction with specified parameters).
[00314] In step S890, the first data center 750 can send the requested transaction data (or the entire block body) to the third data center 950, if determined that this action is acceptable. In other modalities, instead of sending records of real digital assets or block bodies, the first 750 data center can instead send a binary response indicating whether or not a digital asset exists with parameters specified in the
Petition 870190022368, of 03/08/2019, p. 130/158
104/114 accounting book.
[00315] In alternative modalities, instead of removing the block body, the block body (or the transaction data) can be obscured. For example, in step S855, the first data center 750 can obscure the block body. This may include encrypting some or all of the block body, hashing the block body, replacing the block body with false or meaningless information or obscuring the record information. Then, in step S870, the third data center 950 can add the block header and the obscured block body to its blockchain ledger. In some embodiments, if the block body is encrypted the third data center 950 may be able to obtain a key to decrypt the block body. For example, in step S890, the first data center 750 can provide a key to view the block body information.
[00316] Thus, the use of separate data centers can allow a single asset transfer network to have different customizable resources and be used in different groups, even if a group does not want transaction information or block bodies to be shared with other groups. For example, the group can effectively operate a local blockchain (for example, maintained by one or more data centers in that group). Block headers and other unrestricted information can still be shared outside the group for some or all of the transactions, but block bodies cannot be shared. Thus, each data center can still include a master set of block headers that link the different local blockchain ledgers, while the actual block bodies with transaction log information can be kept within the group.
[00317] As explained above, the modalities allow these types of localized and restricted blockchain accounting books to be
Petition 870190022368, of 03/08/2019, p. 131/158
105/114 for any type of application or entity that benefits from greater local privacy. For example, a particular financial institution may want to protect information about its customer's transactions. Consequently, the financial institution can maintain its own blockchain ledger and can only distribute block headers (and non-sensitive transaction data) to a central network operating entity or other institutions.
[00318] As mentioned above, data centers from different groups can have a corresponding ordered sequence of blockchain headers. However, as each data center may have only a partial view of the total set of block bodies, different groups of data centers may not have fully matching blockchain accounting books.
[00319] An example of synchronized, but only partially matched blockchain accounting books is shown in FIG.
11. Six successive blocks of a blockchain are shown. Blocks can represent a blockchain ledger across the network. While the blockchain ledger can represent the entire transaction on the network, each data center can build its own copy of the blockchain and can have a limited display of the transaction data within the blockchain ledger.
[00320] FIG. 11 shows two versions of the same blockchain, a first blockchain built by the first data center 750 and a second blockchain built by the third data center 950. As seen in the figure, the blockchain of the first data center includes the block bodies for block 1, the block 3 and block 5. This may be the result of the first data center 750 having generated block 1, block 3 and block 5.
[00321] In contrast, the third data center 950 does not have the bodies from block to block 1, block 3 and block 5. This may be the result of the first
Petition 870190022368, of 03/08/2019, p. 132/158
106/114 data center 750 having sent the ledger update messages to the third data center 950 which included block headers, but not block bodies. Likewise, the blockchain in the third data center 950 may include the block bodies of block 2, block 4 and block 6, while the blockchain in the first data center 750 may not include these block bodies.
[00322] In other modalities, one of the data centers can be configured to share block bodies. For example, in some embodiments, while the third data center 950 does not receive block bodies from the first data center 750, the third data center 950 can share its block bodies with the first data center 750. This would result in the first data center 750 having all block bodies, while the third 950 data center would still have half the block bodies.
[00323] As shown in FIG. 11, while both blockchains have an incomplete view of the block bodies, both blockchains include the complete set of block headers. This is because, in some modalities, both data centers can provide each other with block headers that they have generated. This allows the two data centers to maintain a complete and running list of block headers, even if they do not manage some of the block headers.
[00324] Arrows in FIG. 11 demonstrate that the first data center 750 can send header 1 to the third data center 950, that the third data center 950 can send header 2 to the first data center 750, and so on. The additional arrows demonstrate how each header can be used as part of the block body in the subsequent block and then how the subsequent block can be used to generate the subsequent header. For example, the third data center 950 can incorporate header 1 (received from the first data center 750) into block body 2. Then, the third data center 950 can create the block header for block 2
Petition 870190022368, of 03/08/2019, p. 133/158
107/114 based on its block body. As a result, through cooperation with the data center, each block in the blockchain can reference the immediately preceding block.
[00325] In some modalities, while data centers may not share sensitive transaction information, data centers may share the previous block header, in addition to the current block header. Thus, data centers can send a part of the block body along with the block header. For example, when the third data center 950 sends header 2 (which the third data center 950 generated) to the first data center 750, the third data center 950 may also include header 1 (which the third data center 950 generated) in the message. As a result, the first data center 750 can confirm that header 2 belongs to a block that is subsequent to block 1, where the first data center 750 stopped. Otherwise, when assembling the blockchain blocks, the first data center 750 can simply trust (for example, based on the scheduled synchronization of the update message) that header 2 belongs to a block that follows immediately and refers to block 1.
[00326] In FIG. 11, the two data centers alternate block generation for all other blocks. However, the modalities allow data centers to trade off block generation in other ways and patterns. For example, the first data center 750 can generate two or more blocks in a row and then send headers for both blocks to the third data center 950. The third data center 950 could wait to generate a new block until it receives an upgrade to the first 750 data center.
[00327] In addition, more data centers may be involved in this blockchain update process. For example, if another data center was added to FIG. 11, each data center can generate each third block.
[00328] As explained above, the modalities of the invention allow
Petition 870190022368, of 03/08/2019, p. 134/158
108/114 that distributed data centers can be used by recording all appropriate types of data elements. For example, data elements that represent up-to-date medical information, information about a newly issued university degree, test results, vehicle registration data, signed exemptions and / or any other suitable type of recordable information can be tracked and recorded. Any suitable type of digital record can be used to document a new data element. Any suitable type of data element record can be shared between data centers, although some data centers can only release record identifiers and not record information.
[00329] One embodiment of the invention is directed to a method. The method comprises the processing, by a first data center computer, a first data element and the creation of a first record of the first data element in a first database. The method also includes sending a message to a second data center computer, indicating that the first record was created. The second data center computer updates a second database based on the message.
[00330] Another embodiment of the invention is directed to a first data center computer configured to perform the method described above.
[00331] Another embodiment of the invention is directed to a method that comprises the processing, by a first data center computer, a first data element and the creation of a first record of the first data element in a first database. The method also includes sending a message first to a second data center computer, indicating that the first record was created. The method also includes receiving a second message from the second data center computer, indicating that a second record for a
Petition 870190022368, of 03/08/2019, p. 135/158
109/114 second data element was created by the second data center computer and updating the first database based on the second message. The method further comprises receiving, by a second data center computer, the first message from the first data center computer indicating that the first record was created and updating a second database based on the first message. The method also includes processing the second data element, creating the second record for the second data element in the second database, and sending the second message to the first data center computer, indicating that the second record has been created.
[00332] Another embodiment of the invention is directed to a system that includes a first data center computer and a second data center computer configured to perform the method described above.
[00333] Another embodiment of the invention is directed to a method. The method comprises the processing, by a first data center computer, of a first digital asset that indicates the transfer of a value from a sender to a recipient. The method also includes recording the first digital asset in a first database and sending a message to a second data center computer, indicating that the first digital asset has been registered. The second data center computer updates the second database based on the message.
[00334] In some modalities, the message sent to the second data center computer includes the digital asset and the second data center registers the first digital asset in a second database. In addition, the first database and the second database include a corresponding set of digital asset records.
[00335] In other modalities, recording the first digital asset in the first database includes generating a first block for a first blockchain, the first block including a header and asset information
Petition 870190022368, of 03/08/2019, p. 136/158
110/114 digital. The message sent to the second data center computer includes the header, but does not include the digital asset information. The second data center generates a second block for a second blockchain, the second block, including the header, but not including the digital asset information. Thus, the first block and the second block include the same header. The first database and the second database can include a corresponding set of block headers, but not a corresponding set of digital asset information. The header can also be generated based on a hash of the digital asset information. Digital asset information can include value information, information about the sender and information about the recipient. The value can include an access privilege.
[00336] The method may also include the receipt, by the first data center computer, of a second digital asset from the second data center computer. The second data center computer processed the second digital asset and added the second digital asset to the second database. The method also comprises the validation of the second digital asset and the recording of the second digital asset in the first database. The method can also include receiving the first digital asset, where the first digital asset is initially received and processed only by the first data center computer and where the second digital asset is initially received and processed only by the second data center computer. In addition, the second data center computer can validate the first digital asset before writing the first digital asset to the second database.
[00337] Another embodiment of the invention is directed to a first data center computer configured to perform the method described above.
[00338] Another modality of the invention is directed to a method that comprises the processing, by a first data center computer, of
Petition 870190022368, of 03/08/2019, p. 137/158
111/114 a first digital asset that indicates the transfer of a value from a sender to a recipient. The method also includes recording the first digital asset in a first database and sending a first message to a second data center computer, indicating that the first digital asset has been registered. The method further comprises receiving a second message from the second data center computer, indicating that a second digital asset has been registered by the second data center computer and updating the first database based on the second message. The additional method includes receiving, by a second data center computer, the first message from the first data center computer indicating that the first digital asset has been registered and then updating a second database based on the first message. The second data center computer can also process the second digital asset, registering the second digital asset in the second database and sending the second message to the first data center computer, indicating that the second digital asset has been registered. The first database and the second database can include corresponding data.
[00339] In some modalities, the first message sent to the second data center computer includes the first digital asset and the second data center registers the first digital asset in a second database. In addition, the second message includes the second digital asset and the update of the first database based on the second message includes the recording of the second digital asset in the first database. In addition, the first database and the second database include a corresponding set of digital asset records.
[00340] In other modalities, recording the first digital asset in the first database includes generating a first block for a first blockchain, the first block including a header and asset information
Petition 870190022368, of 03/08/2019, p. 138/158
112/114 digital. The message sent to the second data center computer includes the header, but does not include the digital asset information. The second data center generates a second block for a second blockchain, the second block, including the header, but not including the digital asset information. Thus, the first block and the second block include the same header. The first database and the second database can include a corresponding set of block headers, but not a corresponding set of digital asset information. The header can also be generated based on a hash of the digital asset information. Digital asset information can include value information, information about the sender and information about the recipient. The value can include an access privilege.
[00341] The method may also include the receipt, by the first data center computer, of a second digital asset from the second data center computer. The second data center computer processed the second digital asset and added the second digital asset to the second database. The method also comprises the validation of the second digital asset and the recording of the second digital asset in the first database. The method can also include receiving the first digital asset, where the first digital asset is initially received and processed only by the first data center computer and where the second digital asset is initially received and processed only by the second data center computer. In addition, the second data center computer can validate the first digital asset before writing the first digital asset to the second database.
[00342] Another embodiment of the invention is directed to a system that includes a first data center computer and a second data center computer configured to perform the method described above.
[00343] A computer system will now be described that can be used to implement any of the entities or components
Petition 870190022368, of 03/08/2019, p. 139/158
113/114 described in this document. The subsystems in the computer system are interconnected through a system bus. Additional subsystems include a printer, keyboard, fixed disk and a monitor that can be attached to the video adapter. Peripherals and input / output (I / O) devices, which can be coupled to the I / O controller, can be connected to the computer system through any number of means known in the art, such as a serial port. For example, a serial port or external interface can be used to connect the computer device to a wide area network such as the Internet, a mouse input device or a digitizer. Interconnection via the system bus allows the central processor to communicate with each subsystem and control the execution of instructions from the system memory or the fixed disk, as well as the exchange of information between the subsystems. The system memory and / or the fixed disk can incorporate a computer-readable medium.
[00344] As described, the service of the invention may involve the implementation of one or more functions, processes, operations or steps of the method. In some embodiments, the functions, processes, operations or steps of the method can be implemented as a result of the execution of a set of instructions or software code by an appropriately programmed computing device, microprocessor, data processor or similar. The instruction set or software code can be stored in a memory or other form of data storage element that is accessed by the computing device, microprocessor, etc. In other modalities, the functions, processes, operations or steps of the method can be implemented by firmware or by a dedicated processor, integrated circuit, etc.
[00345] Any of the software components or functions described in this application can be implemented as software code to be
Petition 870190022368, of 03/08/2019, p. 140/158
114/114 executed by a processor using any suitable computer language, such as, for example, Java, C ++ or Perl using, for example, conventional or object-oriented techniques. The software code can be stored as a series of instructions or commands in a computer-readable medium, such as random access memory (RAM), a read-only memory (ROM), a magnetic medium such as a hard disk or a floppy disk or an optical medium such as a CD-ROM. Any computer-readable medium can reside on or within a single computing device and can be present on or within different computing devices within a system or network.
[00346] While certain exemplary modalities have been described in detail and shown in the accompanying drawings, it should be understood that such modalities are merely illustrative and are not intended to be restrictive of the broad invention, and that that invention should not be limited to specific provisions and constructions shown and described, since various other modifications may occur for those of ordinary skill in the art.
[00347] As used here, a quote from one, one or w / o should be understood as at least one (a), unless the contrary is specifically indicated.

权利要求:
Claims (20)
[1]
1. Method, characterized by the fact that it comprises:
create, through the first data center computer, a block for a first blockchain, in which the block includes a block header and block body; and send, through the first data center computer, a message to a second data center computer indicating that the block was created for the first blockchain, the message including the block header, but not the block body, in which the second block data center computer adds the block header to a second blockchain and where the second data center computer does not add the block body to the second blockchain.
[2]
2. Method according to claim 1, characterized by the fact that the block is a first block, the block header is a first block body and the block header is a first block header, in which the second computer data center creates a second block for the second blockchain, where the second block includes a second block header and where the second block header is the same as the first block header.
[3]
3. Method according to claim 2, characterized by the fact that the second block does not have a block body.
[4]
4. Method according to claim 1, characterized by the fact that the first blockchain and the second blockchain include a corresponding set of block headers, but not a corresponding set of block bodies.
[5]
5. Method, according to claim 1, characterized by the fact that the block header is generated based on a hash of the block body.
[6]
6. Method according to claim 1, characterized
Petition 870190022368, of 03/08/2019, p. 142/158
2/5 due to the fact that the block body includes an earlier header from a previous block on the first blockchain.
[7]
7. Method according to claim 1, characterized by the fact that the block body includes a data element.
[8]
8. Method, according to claim 1, characterized by the fact that the first blockchain is stored in a first database and in which the second blockchain is stored in a second database.
[9]
9. Method, according to claim 2, characterized by the fact that it also comprises:
receive, via the first data center computer, a second message from the second data center computer indicating that the second data center computer created a third block for the second blockchain, the message including a third block header, but not a third body block; and create, through the first data center computer, a fourth block for the first blockchain based on the second message, where the fourth block includes a fourth block header and where the fourth block header is the same as the third block header block.
[10]
10. Method according to claim 9, characterized in that the third block body includes the first block header and in which the third block header is generated based on a hash of the third block body.
[11]
11. System, characterized by the fact that it comprises:
a first data center computer comprising:
a processor; and a computer-readable medium, the computer-readable medium comprising code, executable by the processor, for the implementation of a method comprising:
Petition 870190022368, of 03/08/2019, p. 143/158
3/5 create a first block for a first blockchain, the first block including a first block header and first block body; and send a first message to a second data center computer indicating that the first block was created for the first blockchain , the first message including the first block header, but not the first block body; and a second data center computer comprising:
a processor; and a computer-readable medium, the computer-readable medium comprising code, executable by the processor, for the implementation of a method comprising:
receive the first message indicating that the first block was created for the first blockchain, the first message including the first block header, but not the first block body;
create a second block for a second blockchain, where the second block includes a second block header, where the second block header is the same as the first block header and where the second block does not include the first block body .
[12]
12. System according to claim 11, characterized by the fact that the second block does not have a block body.
[13]
13. System according to claim 11, characterized by the fact that the first blockchain and the second blockchain include a corresponding set of block headers, but not a corresponding set of block bodies.
[14]
14. System according to claim 11, characterized by the fact that the first block header is generated based on a hash of the first block body.
[15]
15. System according to claim 11, characterized
Petition 870190022368, of 03/08/2019, p. 144/158
4/5 by the fact that the first block body includes an earlier header from a previous block on the first blockchain.
[16]
16. System according to claim 11, characterized by the fact that the block body includes a data element.
[17]
17. System according to claim 11, characterized by the fact that the first blockchain is stored in a first database, and in which the second blockchain is stored in a second database.
[18]
18. System, according to claim 11, characterized by the fact that the method executed by the second data center computer also comprises:
create a third block for the second blockchain, the third block including a third block header and third block body;
send a second message to the first data center computer indicating that the third block was created for the second blockchain, the message including the third block header, but not the third block body; and where the method performed by the first data center computer comprises:
receive the second message indicating that the third block was created for the second blockchain, the second message including the third block header, but not the third block body; and creating a fourth block for the first blockchain, where the fourth block includes a fourth block header, where the fourth block header is the same as the third block header.
[19]
19. System, according to claim 19, characterized by the fact that the third block is created after the second block, in which the third block body includes the first block header and in which the third block header is generated with based on a hash of the third body
Petition 870190022368, of 03/08/2019, p. 145/158
5/5 block.
[20]
20. System, according to claim 11, characterized by the fact that the method executed by the second data center computer also comprises:
create a third block for the second blockchain, the third block including a third block header and third block body;
send a second message to the first data center computer indicating that the third block was created for the second blockchain, the message including the third block header and including the third block body; and where the method performed by the first data center computer comprises:
receiving the second message indicating that the third block was created for the second blockchain, the second message including the third block header and including the third block body; and create a fourth block for the first blockchain, where the fourth block includes a fourth block header and a fourth block body, where the fourth block header is the same as the third block header and where the fourth body block is the same as the third block body.

类似技术:

---

公开号 | 公开日 | 专利标题

---

US10715531B2|2020-07-14|Network topology

---

US20200259666A1|2020-08-13|Methods and systems for using digital signatures to create trusted digital asset transfers

---

BR112019004571A2|2019-06-11|method and system.

---

US10558820B2|2020-02-11|System and method for maintaining a segregated database in a multiple distributed ledger system

---

US20210314397A1|2021-10-07|Fund conversion between blockchains

---

US10846416B2|2020-11-24|Method for managing document on basis of blockchain by using UTXO-based protocol, and document management server using same

---

US20210194701A1|2021-06-24|Systems and methods for creating a universal record

---

US10942994B2|2021-03-09|Multicomputer processing for data authentication using a blockchain approach

---

US11159537B2|2021-10-26|Multicomputer processing for data authentication and event execution using a blockchain approach

---

KR101882805B1|2018-07-27|Method for blockchain based management of documents in use of merkle tree structure on the basis of unspent transaction output protocol and document management server using the same

---

JP6873270B2|2021-05-19|Handling of transaction activities based on smart contracts in the blockchain Caution Methods and devices for protecting data

---

US11082221B2|2021-08-03|Methods and systems for creating and recovering accounts using dynamic passwords

---

US20200005290A1|2020-01-02|System and Method for Processing Payments in Fiat Currency Using Blockchain and Tethered Tokens

---

US20220005031A1|2022-01-06|Telecommunication System and Method for Settling Session Transactions

---

US11108566B2|2021-08-31|Methods and systems for using digital signatures to create trusted digital asset transfers

---

US20210258169A1|2021-08-19|Split-key wallet access between blockchains

---

US20200145210A1|2020-05-07|Layered recording networks

---

JPWO2018088475A1|2019-10-03|Electronic authentication method and program

同族专利:

---

公开号 | 公开日

---

AU2017340233A1|2019-01-31|

---

EP3520317A4|2019-10-09|

---

RU2019111909A|2020-11-06|

---

WO2018067232A1|2018-04-12|

---

CN109691008A|2019-04-26|

---

MX2019003721A|2019-09-04|

---

EP3520317B1|2021-05-12|

---

EP3886398A1|2021-09-29|

---

EP3520317A1|2019-08-07|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

JP3736338B2|2000-11-13|2006-01-18|株式会社日立製作所|Packet switch|

---

US11270298B2|2014-04-14|2022-03-08|21, Inc.|Digital currency mining circuitry|

---

WO2015175722A1|2014-05-13|2015-11-19|Nant Holdings Ip, Llc|Healthcare transaction validation via blockchain proof-of-work, systems and methods|

---

US10230526B2|2014-12-31|2019-03-12|William Manning|Out-of-band validation of domain name system records|

---

US9973341B2|2015-01-23|2018-05-15|Daniel Robert Ferrin|Method and apparatus for the limitation of the mining of blocks on a block chain|

---

US9967333B2|2015-03-02|2018-05-08|Dell Products Lp|Deferred configuration or instruction execution using a secure distributed transaction ledger|

---

GB201511964D0|2015-07-08|2015-08-19|Barclays Bank Plc|Secure digital data operations|

---

CN105975868A|2016-04-29|2016-09-28|杭州云象网络技术有限公司|Block chain-based evidence preservation method and apparatus|

---

WO2018085558A2|2016-11-03|2018-05-11|Visa International Service Association|Systems and methods for creating a universal record|US10715531B2|2016-02-12|2020-07-14|Visa International Service Association|Network topology|

---

US11108566B2|2016-02-12|2021-08-31|Visa International Service Association|Methods and systems for using digital signatures to create trusted digital asset transfers|

---

US10693658B2|2016-02-12|2020-06-23|Visa International Service Association|Methods and systems for using digital signatures to create trusted digital asset transfers|

---

WO2018085558A2|2016-11-03|2018-05-11|Visa International Service Association|Systems and methods for creating a universal record|

---

EP3605945A1|2018-08-03|2020-02-05|Dovetail Digital Limited|Method and system for exchanging data|

---

CN109039648B|2018-08-03|2021-09-03|克洛斯比尔有限公司|Block chain creating method and device and readable storage medium|

---

US11227282B2|2018-08-20|2022-01-18|Probloch LLC|Time-bounded activity chains with multiple authenticated agent participation bound by distributed single-source-of-truth networks that can enforce automated value transfer|

---

GB2577751A|2018-10-05|2020-04-08|Dragon Infosec Ltd|A consensus method and framework for a blockchain system|

---

GB2587541A|2018-10-05|2021-03-31|Dragon Infosec Ltd|A consensus method and framework for a blockchain system|

---

CN110011930A|2019-03-12|2019-07-12|深圳前海微众银行股份有限公司|The load-balancing method and device of multi-joint alliance's chain in a kind of block chain|

---

CN112487492A|2019-04-04|2021-03-12|创新先进技术有限公司|Data verification method, system and equipment|

---

US10917231B2|2019-04-04|2021-02-09|Advanced New Technologies Co., Ltd.|Data storage method, apparatus, system and device|

---

US11055277B2|2019-04-04|2021-07-06|Advanced New Technologies Co., Ltd.|Integrity verification method, apparatus, and system and device for data in a blockchain-type ledger|

法律状态:
2020-12-22| B11A| Dismissal acc. art.33 of ipl - examination not requested within 36 months of filing|

---

2021-03-09| B11Y| Definitive dismissal - extension of time limit for request of examination expired [chapter 11.1.1 patent gazette]|

---

2021-10-05| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US15/283,930|US10693658B2|2016-02-12|2016-10-03|Methods and systems for using digital signatures to create trusted digital asset transfers|

---

US201762490487P| true| 2017-04-26|2017-04-26|

---

PCT/US2017/046364|WO2018067232A1|2016-10-03|2017-08-10|Network topology|

---